Covenant is a contract linter/proxy for MCP servers, not itself a production tool server. The 4 example tools (get_account, get_weather, convert_currency, get_transactions) are minimal demonstrations in examples/mcp_server.py. All have basic schemas with required parameters and descriptions (10-50 chars), but lack depth: no output schemas documented, no error handling guidance, no parameter constraints (enums, ranges), and descriptions are generic. Naming follows verb_noun convention (good). Parameters are typed but underdescribed. No tool annotations. The server's actual value is as a contract enforcement proxy, not as a tool provider, the example tools are stubs.

• Add output schemas for all tools. Document the structure of returned objects (e.g. get_account returns {account_id, balance, currency, last_updated}). This is critical for LLM planning.
• Expand parameter descriptions to 50-200 chars. For account_id, specify: 'The account identifier (string, 8-12 alphanumeric characters, e.g. ACC123456)'. For city, add: 'City name (string, 1-100 chars; e.g. New York, London).'
• Add enum constraints for convert_currency.to_currency. Define valid currency codes: ['EUR', 'GBP', 'JPY', 'CAD', ...] so LLMs pick from a known set instead of guessing.
• Document error cases and recovery paths. E.g. 'If account_id is not found, the tool returns {error: "Account not found"}. Try search_accounts() with a partial name.' This guides LLM retry logic.
• Add tool annotations (readOnlyHint=true for all four, since they are read-only per the Risk field). This signals to clients that these tools are safe to call without confirmation.

Inferred effective spec: 2026-07-28+.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry