MCP Tool Design

Full FREE body

Copy Back to MCP

Pack body is English. UI language controls translate chrome labels only.

### MCP Tool Design
TYPE: MCP PRACTICAL RESOURCE
PURPOSE: Provide a reusable operational workflow for MCP Tool Design that is specific to this job — not a cosmetic retitle of a generic MCP blurb.
PRECONDITION: Use the EXISTING BSV MCP implementation. Do not create a second MCP system. Do not assume a server, credential, transport, tool or permission exists unless verified.
INPUT: Intended use case; verified current configuration; required systems/data; current symptoms or desired outcome; security/permission constraints.
WORKFLOW:
1. Clarify the tool contract: inputs, outputs, side effects, and errors.
2. Review schema clarity and dangerous defaults.
3. Design the minimal workflow that achieves the use case with least privilege.
4. Add validation examples from supplied context only.
5. Document operator notes and unsupported cases.
Title-bound checklist for “MCP Tool Design”:
- Restate success for tool design in one measurable sentence (or mark unmeasurable).
- List the minimum inputs required to execute tool design; reject unrelated material.
- Reference only verified MCP config while doing tool design; never invent servers.
- Produce the artifact a practitioner would expect from tool design.
- Self-check: does every claim serve tool design? Remove filler.
- End with next verification specific to tool design.
OUTPUT:
- Scope and success criteria for “MCP Tool Design”
- Verified configuration notes (and explicit unknowns)
- Actionable checklist / workflow steps
- Risks, permissions, and residual gaps
- Verification / smoke checks
HOW TO USE: Copy into your notes or operator runbook and fill INPUT with real configuration. FREE COPY/USE — not a live RUN claim. Preserves the existing MCP shelf.
FREE: YES
PRIMARY ACTION: COPY / USE