PromptContract MCP server — enhance_prompt tool + boost-* prompts, stdio JSON-RPC, zero dependencies
Single tool 'enhance_prompt' has a well-structured input schema with 4 parameters, all typed and described. Tool description is clear (127 chars) and explains the action, prerequisites, and output. However, the output schema is not documented, the description states 'Returns only the enhanced text' but does not specify the response structure (is it a string? an object with a 'text' field?). Parameter descriptions are adequate but lack format/constraint details (e.g., what are valid profile values beyond 'coding-agent'?). No error handling guidance is visible, what happens if the API key is missing or the provider fails? The tool follows basic naming conventions (verb_noun) and avoids secrets in parameters (uses env vars), but lacks the depth expected of production-grade tools.
Rewrite a vague user prompt into a clear, specific, executable prompt. Returns only the enhanced text. Requires a configured provider (CONTRACT_API_KEY/CONTRACT_PROVIDER or config file).
Output schema not documented. Description says 'Returns only the enhanced text' but does not specify whether response is a plain string or a structured object. LLMs cannot plan downstream operations without knowing the response shape.
Parameter 'profile' lacks enumeration of valid values. Description mentions 'default: coding-agent' but does not list other accepted profiles. LLMs will guess or hallucinate invalid values.
No error handling guidance. What happens if CONTRACT_API_KEY is missing, the provider is unreachable, or the LLM call fails? Tool description does not explain recovery steps or error categories (retryable vs fatal).
Parameter 'context' description is vague ('Optional background context (e.g. repo summary)'). Does not specify format, max length, or how it is assembled into the prompt. LLMs may pass unstructured or oversized context.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 64 | 2026-07-28+ | v2 |
STDIO transport only. Server is not remotely accessible and cannot be used by hosted MCP clients. Limits deployment flexibility and testing.