Skip to main content

Appendix B — MCP Tool Definition Template

Use this template when publishing a capability as an MCP tool.

  • Tool name (capability name + version):
  • Purpose / outcome:
  • Input schema (JSON schema reference):
  • Output schema (JSON schema reference, include confidence/provenance fields):
  • Supported execution modes: deterministic, AI-assisted
  • Required context fields:
  • Policy constraints (data classification, rate limits, allowed environments):
  • Owner:
  • Versioning policy:
  • Audit and logging requirements:
  • Test cases / contract tests:
  • Migration / deprecation notes: