Odile Gate

Apply an odile.yaml

gate_sync_declarative

Idempotent

Make a Gate project match an odile.yaml: creates the project (if no project_id) and missing apps and approvers, applies run mode, loop, learning and anomaly-guard settings and alerts. Example plugin: {name: anomaly-guard, settings: {mode: alert, z_threshold: 4, min_minutes: 3, half_life: 60}}. Never revokes or deletes; differences it cannot apply (an app's routes or rate limit) come back as drift. dry_run lists the steps without changing anything. New keys are shown once.

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": {
      "config": "<config>"
    },
    "name": "gate_sync_declarative"
  }
}

Input Schema

Name	Required	Description
`config`	Yes	The whole odile.yaml (or the same as JSON) as text
`dry_run`	No	List the steps without changing anything
`admin_key`	No	Its admin key (ga_...), required with project_id. Read it from the .env; never print it.
`project_id`	No	Optional: an existing project to sync

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 21, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Adds substantial behavior beyond annotations: creates missing project/apps/approvers, applies settings, never revokes or deletes, returns unappliable differences as drift, and shows new keys once. These details clarify the mutation and idempotent behavior despite annotations already covering safety hints.

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

Conciseness4/5

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

Front-loads the purpose and keeps supporting details compact. The plugin example is useful, though the second sentence is dense and slightly overpacked with multiple behavioral clauses.

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

Completeness4/5

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

For a complex mutation tool with no output schema, the description covers creation, applied settings, drift behavior, dry_run, and key visibility. It could be more explicit about return shape, but auth expectations are covered by the schema and the main risks are disclosed.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics for project_id by explaining that omitting it creates a project. The inline plugin example also clarifies config structure beyond the schema description.

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: make a Gate project match an odile.yaml. It also explains the conditional creation behavior and full-sync scope, which clearly distinguishes it from sibling tools like gate_create_project, gate_add_app, and gate_validate_config.

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?

Gives clear usage context for applying a full declarative config and notes that dry_run previews steps. However, it does not explicitly route the agent versus gate_validate_config or say when not to use this in favor of narrower sibling tools.

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?