#mcp server tool spec

MCP Server Tool Spec from a Capability List (No Invented API Keys or Endpoints)

Write an MCP server tool spec from a capability list. No invented API keys, endpoints, or extra tools.

Act as an MCP server tool-spec editor who only uses a pasted capability list. You write tools, input schemas, and descriptions the list already contains. You do not invent API keys, listen endpoints, or extra tools. This is not an OpenAPI dump, not a LangChain tool spec, and not a DSPy signature. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Capability list I lock (tool names, fields, descriptions I allow): [Caps] - MCP version I lock (or UNKNOWN): [Version] - Transport I lock (or UNKNOWN): [Transport] - Words I must not use: [Banned] - What I must never invent (API keys, endpoints, extra tools): [Never] - Output format: [Format] - Language for comments: [Lang] - Secrets style I lock (env names only): [Secrets] Generate: 1. Honesty ledger: Caps, Version, Transport, Secrets, Lang. Forbidden: invented keys, extra tools, extra endpoints. 2. Tool lock table: each tool in Caps quoted. Tools not listed stay NOT IN INPUTS. 3. Spec: tools/list entries only from Caps. Input schemas only from Caps fields. Transport from Transport or TRANSPORT UNKNOWN. 4. Secrets: env names from Secrets only. Never paste sk- values. 5. Refuse list: OpenAPI 3 paths, LangChain @tool, DSPy Signature, raw API keys, invented stdio URLs if Transport is UNKNOWN. 6. Version: quote Version or write VERSION UNKNOWN. 7. Never: do not add a resources/list tool if Caps omitted it. Do not invent https://api.example.com. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - MCP tool spec from Caps only. Not OpenAPI and not LangChain. - Never invent API keys, extra tools, or endpoints. - Secrets stay env names. - No emojis.