Odile Gate

Choose response fields for an app

gate_set_response

Idempotent

Opt-in JSON response redaction: return only explicit JSON Pointer paths, e.g. /id and /items/*/name. * matches one segment; selecting a container allows its whole subtree. Applies to every upstream response for this app, including errors. Maximum 1 MiB and 5 seconds to read; invalid/non-JSON responses are withheld. No bodies are stored. A withheld reply never reverses an upstream write. null disables filtering. Free and Pro.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>",
      "admin_key": "<admin_key>",
      "app": "<app>",
      "allow": "<allow>"
    },
    "name": "gate_set_response"
  }
}

Input Schema

Name	Required	Description
`app`	Yes	The app id (app_...)
`allow`	Yes
`admin_key`	Yes	The project admin key (ga_...). Read it from the .env; never print it.
`project_id`	Yes	The project id from gate_create_project, e.g. p1a2b3...

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 22, 2026

TDQS

A4.8/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds substantial behavior beyond annotations: scope covers all upstream responses including error bodies, there are 1 MiB / 5 second limits, invalid or non-JSON responses are withheld entirely, no bodies are stored, and withholding never reverses an upstream write. That last sentence is exactly the reassurance an agent needs before applying a filter that can suppress data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Every sentence carries distinct information — syntax, scope, limits, storage, failure semantics, disable path, availability — with the core definition front-loaded. The trailing 'Free and Pro' note is terse but not wasteful; there is no filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutating config tool with annotations and no output schema, the description covers limits, edge-case failure behavior, reversibility concerns, and how to turn the feature off. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 75% and the undocumented parameter is `allow`, which the description fully compensates for: JSON Pointer syntax with an example, single-segment `*` wildcard semantics, whole-subtree behavior when selecting a container, and null as the disable value. This is meaning the schema does not provide.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: opt-in JSON response redaction configured per app using explicit JSON Pointer allow paths. It immediately distinguishes itself from sibling config tools (gate_set_app_runs, gate_add_app) by scoping to 'every upstream response for this app'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Opt-in' plus 'null disables filtering' tells the agent both the enabling and disabling condition, which is the key usage decision. It stops short of naming when a sibling configuration tool should be preferred, but for a single-purpose setting tool the use case is unambiguous.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Odile Gate tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?