Odile Labs

Read a request

get_request

Idempotent

Read a request you hold a grant on: objective, attempts, facts, booking, your_scope and next_allowed. It checks any booking against the business calendar and updates the stored record and billing to match, but never books, moves or cancels anything and contacts nobody; repeat it freely. Use it after a booking, and after claim_request, before acting. Not for a conversation started without a request (get_replies). next_allowed is book, cancel, read or needs_human; a fact marked uncertain means the calendar could not confirm it. Refused with grant_required or grant_revoked when you have no live grant. Requires direct:tasks.

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": {
      "request_id": "<request_id>"
    },
    "name": "get_request"
  }
}

Input Schema

Name	Required	Description	Default
`request_id`	Yes	The request_id returned by open_request or shared by the assistant that opened it.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 2, 2026

addedInput schema / properties / request_id / description

Added value: +"The request_id returned by open_request or shared by the assistant that opened it."

AddedNov 2, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Discloses side effects beyond the annotations: it reconciles the stored record and billing against the business calendar, yet 'never books, moves or cancels anything and contacts nobody; repeat it freely' — consistent with idempotentHint=true and destructiveHint=false. It also names refusal modes (grant_required, grant_revoked) and the required scope (direct:tasks), which annotations do not convey.

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 purpose and returned fields, then side effects, then usage, then error/auth notes — a sensible ordering with no filler. The middle sentence is long and runs several clauses together, slightly taxing to parse, but every clause carries real 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?

No output schema exists, and the description compensates by listing returned fields and decoding the important one ('next_allowed is book, cancel, read or needs_human') plus the meaning of uncertain facts. Side effects, refusal reasons, and auth scope are all covered, leaving nothing an agent needs unstated.

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% and the single request_id parameter is already documented in the schema as coming from open_request. The description adds no format, syntax, or provenance detail beyond that, so the 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 and resource ('Read a request you hold a grant on') and immediately enumerates what comes back: objective, attempts, facts, booking, your_scope, next_allowed. It also names the sibling it is not for (get_replies), so an agent can distinguish it without opening the schema.

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 explicit trigger conditions ('after a booking, and after claim_request, before acting') and an explicit exclusion ('Not for a conversation started without a request (get_replies)'), naming the alternative tool. When-to-use, when-not-to-use, and the substitute are all present.

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

All Odile Labs 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?