Remote control room, agent inspector, and multi-provider model router for Claude Code
This server exposes 12 tools across 5 template categories (file ops, KV store, REST API, greeting, user interaction). Most tools have basic descriptions (10-50 chars) and minimal parameter documentation. Input schemas are present but sparse: parameters lack detailed descriptions, enums are absent where needed, and output schemas are undocumented. No tool annotations (readOnlyHint, destructiveHint, idempotentHint). Error handling is generic. The 'hello' tool is a placeholder; file/KV/HTTP tools are templates, not production-hardened. Naming is reasonable (verb_noun pattern) but descriptions are too terse to guide LLM selection effectively.
Ask the user a question and get their response
A simple test tool that greets by name
Fetch JSON from a GET endpoint. Base URL: https://jsonplaceholder.typicode.com
Send a POST request with JSON body. Base URL: https://jsonplaceholder.typicode.com
Delete a key
Get a value by key
List all keys in the store
Parameter descriptions are minimal or absent. 'path' in read_file is described as 'Relative path from ROOT_DIR' but lacks guidance on format, length limits, or path traversal constraints. LLMs cannot infer whether '../' is allowed or what happens with absolute paths.
No output schemas documented. Tools return unstructured responses (e.g., 'List files in a directory' does not specify whether it returns an array of strings, objects with metadata, or a single concatenated string). LLMs cannot plan downstream calls without knowing response structure.
Destructive operations (write_file, kv_delete) lack confirmation or dry-run support. No tool annotations (destructiveHint) to signal to clients that these calls have irreversible side effects. Agents may accidentally overwrite or delete data.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 51 | 2026-07-28+ | v2 |
Set a key-value pair
List files in a directory
Read the contents of a file
Search for files containing a text pattern
Write content to a file (creates or overwrites)
No input validation constraints. 'pattern' in search_files is free-form; no regex, length limit, or character restriction stated. 'headers' in http_post is an object with no schema, LLMs cannot know what keys are valid or what values are expected.
Tool descriptions are too terse (10 - 50 chars). 'Get a value by key' (18 chars) does not explain when to use kv_get vs read_file, what the key format is, or what happens if the key does not exist. Descriptions should be 50 - 200 chars and answer WHAT, WHEN, and WHAT-IF.