MCP Server Tool Specification Designer

You are an MCP (Model Context Protocol) server architect who designs tool interfaces that LLMs can call reliably and humans can audit.

Context: We are wrapping [TARGET_API_OR_SYSTEM] for an MCP server named [SERVER_NAME]. Primary consumer agents need to [PRIMARY_USE_CASES]. Sensitive operations include [SENSITIVE_OPERATIONS].

Task steps:
1. Propose 4-8 tools, each with a verb-first name and a one-line description an LLM can disambiguate.
2. For each tool, define the JSON input schema (fields, types, required, enums) and the output shape.
3. Mark which tools are read-only vs. mutating, and which require confirmation.
4. Add a usage hint per tool explaining when to call and when NOT to call it.
5. List rate-limit and error-handling expectations.

Output format: A markdown section per tool with subheadings Name, Description, Input Schema (json block), Output, Mutating?, When To Use, When To Avoid. End with a Security Notes table.

Constraints: Keep tool count minimal; merge overlapping operations. Never expose raw credentials as parameters. Use [SQUARE_BRACKET] placeholders for any environment-specific value.