Skip to main content
Glama
Sign In

Odile Gate Oversight

by com.odilelabs
OverviewDiscussionsAdmin

Read run timeline

gate_get_run_timeline
Read-only

Returns one run's call metadata, approvals and approver names, recovery outcomes and delegated children; use it to reconstruct that session instead of gate_read_audit's project-wide calls or gate_get_run_tree's permission state. No bodies or query values. One run only; the project-wide log is gate_read_audit.

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

Input Schema

NameRequiredDescriptionDefault
beforeNoOlder audit events (timeline pages have at most 500 events)
run_idYesThe run id
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. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral information beyond that: the exclusion of bodies and query values, and the one-run-only scope. It does not discuss pagination or ordering, though the schema's `before` parameter partially covers paging.

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?

Three tight sentences, front-loaded with the returned payload before the routing guidance. The closing clause ("One run only; the project-wide log is gate_read_audit") somewhat repeats the earlier sibling contrast, costing a bit of economy.

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 carries the return-value burden and does so by enumerating the payload sections and the explicit exclusions (no bodies or query values). For a read-only timeline tool with fully documented parameters, nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, including the `before` cursor and the 500-event page cap, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond noting the single-run scope, which justifies the baseline 3.

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 ("Returns one run's call metadata, approvals and approver names, recovery outcomes and delegated children") and enumerates the payload sections, so an agent knows exactly what it gets. It also explicitly names the two siblings it is not (gate_read_audit for project-wide calls, gate_get_run_tree for permission state).

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?

Gives an explicit selection rule: "use it to reconstruct that session instead of gate_read_audit's project-wide calls or gate_get_run_tree's permission state." The final sentence reinforces the single-run scope versus the project-wide log, leaving no ambiguity about when to pick this tool.

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

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