Synapse is a gRPC-based agent platform, not an MCP server. The 5 tools (GetToolPolicy, PutToolPolicy, ReloadToolPolicy, ListAdminTools, ListToolCatalog) are internal gateway handlers for policy management. Tool definitions are inferred from handler names and brief descriptions in source comments, not from explicit MCP tool registration. No JSON Schema input definitions are visible in the provided code. Descriptions are present but minimal (10-50 chars), lacking WHEN/WHY context. No output schemas documented. This is a policy control plane, not a chat-facing agent tool interface.

• Register tools explicitly with MCP protocol using formal JSON Schema for all inputs. Define role_allow as object with string keys and array values; approval_required and disabled_tools as string arrays; description as string.
• Expand tool descriptions to 100-200 chars. Example: 'GetToolPolicy: Retrieve the current tool policy configuration. Use this to audit which tools are enabled, disabled, or require approval for each role. Returns role permissions, approval requirements, and disabled tool list.'
• Document output schemas for ListAdminTools and ListToolCatalog. Specify that each tool object includes: name (string), risk_level (enum: low|medium|high|critical), requires_approval (boolean), allowed_for_role (boolean), currently_disabled (boolean), disabled_reason (string).
• Add parameter descriptions for PutToolPolicy inputs: 'role_allow: Map of role names (string keys) to arrays of tool names (string values). Use wildcard "*" to allow all tools for a role. Example: {"admin": ["*"], "user": ["ListToolCatalog", "GetToolPolicy"]}.'
• Add error recovery guidance: 'If PutToolPolicy fails with validation error, call ListAdminTools to verify tool names. If ReloadToolPolicy times out, check gateway logs and retry after 30 seconds.'