Static source inference · medium confidence · evidence: Streamable HTTP
Current-spec patterns detected
Summary
This server exposes 7 tools via HTTP (Cloudflare Workers). While schemas and basic descriptions are present, there are significant gaps in LLM-optimized descriptions, parameter documentation, and output schema clarity. Most tool descriptions are under 50 characters and lack context about when to use them or what they return. Parameters often lack descriptions entirely. Error handling is minimal. The naming is reasonable but descriptions are far below the 194-char baseline for A+ tools. This is a template/skeleton implementation, not production-grade.
Tools (7)
apiread onlysource verified40/100
Echo method and query. Optional query object and method.
get-kvread onlysource verified66/100
Get Key Value from storage
helloread onlysource verified57/100
Return greeting and time. Optional query param: name.
http-requestwritesource verified75/100
Perform an outbound HTTP request with method, headers, query, and body/json.
Many parameters lack descriptions entirely. 'query' in api.ts has no type description for its nested object values. http-request params are documented but output schema is missing.
Generic tool names reduce LLM discoverability. 'ping' (11-char description), 'api', and 'weather' do not start with clear action verbs. 'ping' especially is vestigial.
No output schemas documented. LLMs cannot plan downstream calls or extract required fields. http-request, get-kv, set-kv, weather all lack response structure docs.
Recommendations
Expand tool descriptions to 100-200 characters. Example for 'hello': 'Fetches a personalized greeting with the current server time. Pass an optional name parameter to customize the greeting. Useful for testing connectivity and checking server uptime.'
Add descriptions to ALL parameters. For api.ts 'query' param: 'Object of query string key-value pairs. Each key and value must be a string (e.g., {"search": "term", "limit": "10"}).'
Document output schemas for every tool. For get-kv: 'Returns {"key": string, "value": string, "expirationTtl": number | null, "createdAt": ISO8601 timestamp}.' For weather: 'Returns {"location": string, "temperature": number (Celsius), "condition": string, "humidity": number (0-100), "fetchedAt": ISO8601 timestamp}.'
Rename 'api' to 'call_http_api' or 'proxy_api' to distinguish it from http-request (which is more powerful). If they overlap, consolidate into one tool.
Rename 'weather' to 'get_weather' and add parameter 'location' (optional, default 'Hà Nội, Việt Nam') to make it more flexible and discoverable.
Rename 'ping' to 'health_check' or remove it entirely (duplicate of /health endpoint).
Add explicit state-change markers to set-kv and http-request descriptions. For set-kv: 'WRITES data to Cloudflare KV storage. This is an irreversible operation that overwrites any existing value for the given key.'
Add error recovery hints. For get-kv: 'If key not found, returns null. If storage is unavailable, returns error with code STORAGE_UNAVAILABLE, retry after 5 seconds or check Cloudflare status.'
No error handling guidance. Tools return raw errors (e.g., 'Not implemented', HTTP status codes) without recovery hints. LLMs cannot self-correct on failures.
Mutation tools (set-kv, http-request with POST/DELETE) lack explicit state-change warnings in descriptions. LLMs may not realize these are irreversible.
No tool annotations (readOnlyHint, destructiveHint, idempotentHint) present. Cannot signal to agents which tools are safe to call speculatively.
helloapipingget-kvset-kvhttp-requestweather
Add tool annotations (via a hypothetical future extension or in descriptions). Example: 'readOnlyHint: true' for hello, ping, get-kv, weather. 'destructiveHint: true' for set-kv.
Document parameter constraints. For http-request 'url': 'Valid http:// or https:// URL (max 2048 chars). No credentials in URL, use headers for auth.' For 'method': 'One of: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS (default GET).'
Add pagination guidance to tools that could return large results. Future: if weather or api tools grow to return lists, add limit and offset/cursor params.
Clarify mutual exclusivity in http-request: 'body and json are mutually exclusive. Use body for raw text/binary; use json for JSON payloads (automatically sets Content-Type).'
Remove or implement the 'ping' tool. If kept, expand description to explain its purpose and use-case over the /health endpoint.