# io.github.hengkp/rtcf

> Turns rough requests into sharp Role/Task/Context/Format prompts. Thai and English.

- name: io.github.hengkp/rtcf
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 90/100
- quality: 79/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.hengkp%2Frtcf
- tools: https://api.protogrid.dev/v1/servers/io.github.hengkp%2Frtcf/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "rtcf": {
      "type": "http",
      "url": "https://rtcf.happlen.com/api/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 65
- provenance: 90
- drivers: +repository +namespace-matches-repo +website +reachable +uptime-100% ~updated-99d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 79/100 (good)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 71 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- fail `tools.annotations`: no tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: improve_followup (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); build_prompt (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); improve_prompt (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
- pass `tools.token_cost`: about 672 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 3, about 672 tokens to load them all
- tool set hash: 51fb8562a604e878b47282f2ff9dd28e
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.hengkp/rtcf.svg)](https://protogrid.dev/servers/io.github.hengkp/rtcf)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://rtcf.happlen.com/api/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (3)

- `build_prompt`: Compose a ready-to-use prompt from explicit Role, Task, Context, and Format parts. Use when the user already knows the pieces and wants them woven into one clean prompt.
- `improve_followup`: Write the user's NEXT message for an AI conversation that is already in progress (a follow-up). Use when the user wants to refine, deepen, or continue earlier work in this conversation. Do NOT use it for a brand-new task (use improve_prompt for that). Returns a short, ready-to-send continuation message that anchors to the existing work instead of restarting it. Requires an API key (add ?key=rk_live_... to the connector URL).
- `improve_prompt`: Rewrite a rough prompt into a sharper, ready-to-use prompt structured as Role, Task, Context, Format (RTCF). Returns the improved prompt, its four parts, a short list of clarifying questions worth asking the user, and which model tier and effort level suit this kind of work. Use this before answering when the user's request is vague, or when the user asks to improve a prompt.