Skip to main content
Glama
Sign In

Odile Gate

by com.odilelabs
OverviewDiscussionsAdmin

Check an agent integration setup

gate_check_setup
Read-onlyIdempotent

Read actual Gate protection settings before giving an integration production access. Reports observe-only mode, writes without mandatory runs, missing user-token configuration, wildcard grants and approval separation, with evidence, exact remedies and explicit limits. Sends no upstream requests, changes no settings and uses no gateway quota. Configuration-only: not a security certificate or runtime enforcement test. Use it on a live project; to check an odile.yaml before applying it use gate_validate_config.

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>"
    },
    "name": "gate_check_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault
appNoOptional: check one active app id (app_...) instead of all active apps
admin_keyYesThe project admin key (ga_...). Read it from the .env; never print it.
project_idYesThe project id from gate_create_project, e.g. p1a2b3...

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds value beyond them: no upstream requests, no settings changes, no gateway quota consumption. It also sets explicit scope limits ('not a security certificate or runtime enforcement test') and enumerates what is reported.

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?

Three dense, front-loaded sentences with no waste: purpose first, then what it reports, then explicit limits and the sibling alternative. Every sentence carries distinct information.

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?

With no output schema, the description compensates by enumerating the findings returned (observe-only mode, writes without mandatory runs, wildcard grants, approval separation) plus evidence and remedies. It also states the non-effects and the scope boundary, which is everything needed to decide and call correctly.

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

Parameters3/5

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

Schema coverage is 100%, so all three parameters (app, admin_key, project_id) are already documented in the schema. The description adds no parameter-level detail such as the effect of omitting 'app' or how admin_key is used, so baseline 3 applies.

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+resource ('Read actual Gate protection settings') and a concrete moment of use ('before giving an integration production access'). It is clearly distinguishable from gate_validate_config, which is named as the static-config counterpart.

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

Usage Guidelines5/5

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

Explicitly routes the agent: 'Use it on a live project; to check an odile.yaml before applying it use gate_validate_config.' Both the when-to-use and the when-not-to-use alternative are spelled out.

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

All Odile Gate toolsInspect
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