🤖 AI Tools
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.
0Reviews
Prompt
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.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Caps: tool name=extract_ticket; inputs=raw_text as pasted; outputs=title, priority as pasted. resources/list NOT IN INPUTS. Second tool NOT IN INPUTS. Version: UNKNOWN (do not invent 2024-11-05) Transport: UNKNOWN (do not invent stdio) Banned: sk-, always, guaranteed, example.com Never: invent API keys, invent extra tools, invent endpoints Format: ledger + tool-lock + spec + refuse + gaps Lang: English comments Secrets: MCP_API_KEY env name only as pasted. No raw key.
Example Output
1. Ledger. Caps: extract_ticket; inputs raw_text; outputs title, priority. resources/list NOT IN INPUTS. Second tool NOT IN INPUTS. Version UNKNOWN. Transport UNKNOWN. Secrets MCP_API_KEY env. Lang English. Forbidden: sk-, always, guaranteed, example.com, extra tools, extra endpoints.
2. Tool lock. extract_ticket KEEP. resources/list NOT IN INPUTS. Second tool NOT IN INPUTS.
3. Spec sketch.
# VERSION UNKNOWN. TRANSPORT UNKNOWN. Do not invent stdio or https://api.example.com.
tools/list:
name: extract_ticket
inputSchema: { raw_text: string as pasted }
description: extract title and priority as pasted
# other tools omitted. NOT IN INPUTS.
# MCP_API_KEY env name only.
4. Secrets. MCP_API_KEY env. No sk- value.
5. Refuse. OpenAPI paths: refused. LangChain @tool: refused. DSPy Signature: refused. stdio invented: refused. https://api.example.com: refused. sk- key: refused.
6. Version. VERSION UNKNOWN.
7. Never. No resources/list. No second tool. No minted endpoint.
8. Compliance. Banned hits none. Format ledger+tool-lock+spec+refuse+gaps. Gaps: MCP version, transport, extra output keys, resources/list, second tool.
Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.