agent_schema_enforcer — Diogenes Gateway MCP Tool
agent_schema_enforcer
(agent schema enforcer) is one of 15 tools on the
Diogenes Gateway
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call agent_schema_enforcer from your client
- Claude Code Diogenes Gateway agent_schema_enforcer run in your project directory
- Claude Desktop Diogenes Gateway agent_schema_enforcer ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Diogenes Gateway agent_schema_enforcer ~/.cursor/mcp.json
- VS Code Diogenes Gateway agent_schema_enforcer .vscode/mcp.json
- Zed Diogenes Gateway agent_schema_enforcer ~/.config/zed/settings.json
- Windsurf Diogenes Gateway agent_schema_enforcer ~/.codeium/windsurf/mcp_config.json
- Cline Diogenes Gateway agent_schema_enforcer ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Diogenes Gateway agent_schema_enforcer ~/.gemini/settings.json
- Grok Diogenes Gateway agent_schema_enforcer .mcp.json (in your project root)
- ChatGPT Diogenes Gateway agent_schema_enforcer Settings → Connectors → Advanced → Developer mode
- Claude.ai Diogenes Gateway agent_schema_enforcer Settings → Connectors → Add custom connector
- LangChain Diogenes Gateway agent_schema_enforcer pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http diogenes-gateway https://diogenes-l402-gateway.corinth.workers.dev/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 18 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.