Odile Gate

List held actions

gate_list_actions

Read-only

Actions waiting for approval (or in another state), with the exact call. With an installed approval-risk model, pending actions sort by risk descending and include risk (0–1) and risk_features (top two advisory signals). No model means no score and newest first. Only a person decides in the dashboard.

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_list_actions"
  }
}

Input Schema

Name	Required	Description
`state`	No	Default: pending
`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.

First observedOct 20, 2026

TDQS

A4.3/5.0

Behavior5/5

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

It provides highly valuable behavioral details beyond the annotations, specifically describing the conditional sorting (risk descending vs. newest first) and the inclusion of specific output fields like 'risk (0–1) and risk_features.' This offers deep insights into the tool's return 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?

The definition is efficient, front-loading the core behavior and then providing logical extensions (risk model behavior, default state, and business constraints) in a well-structured flow. Every sentence contributes meaningfully to the understanding of the tool's operation.

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?

Given the complexity of how this tool's output changes based on the risk model, the description is highly complete. It manages to explain both the base functionality and the advanced, conditional behaviors relevant to the agent.

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?

With 100% schema coverage, the baseline score of 3 is appropriate. The description clarifies the optional `state` parameter's role in defining what actions are listed, but does not add specific syntax or semantic depth beyond what the enum already describes.

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

Purpose4/5

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

The description clearly states the purpose is to list 'Actions waiting for approval (or in another state)' and specifies which actions are held, making the function unambiguous. Although it doesn't explicitly list siblings, the specific focus on 'held actions' provides clear scope.

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?

It explains that the tool's behavior changes based on an external factor—the presence of an 'approval-risk model.' This guides the agent on expected outcomes under different environmental conditions, allowing for more precise query formulation.

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?