Skip to main content
Glama
Sign In

Conductor Relay MCP

by io.github.Zman504
OverviewDiscussionsAdmin

Verify Direct Offer

verify_direct_offer
Idempotent

Execute the canonical Direct Session verify_direct_offer operation. Requires an Authorization: Bearer header.

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": {
      "offer_id": "<offer_id>",
      "challenge_id": "<challenge_id>",
      "challenge": "<challenge>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "verify_direct_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
offer_idYesCanonical offer id argument for the verify_direct_offer Direct Session operation.
challengeYesCanonical challenge argument for the verify_direct_offer Direct Session operation.
challenge_idYesCanonical challenge id argument for the verify_direct_offer Direct Session operation.
idempotency_keyYesRequired mutation idempotency key, shared across REST, MCP, and A2A.

Output Schema

NameRequiredDescriptionDefault
okYesTrue when the upstream exchange call succeeded (HTTP status < 400).
dataYesCanonical verify_direct_offer result. Null when ok is false.
errorYesIn-band error code or message when ok is false; null on success.
statusYesUpstream HTTP status code returned by the Conductor Relay API.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / challenge / description
      Added value: +"Canonical challenge argument for the verify_direct_offer Direct Session operation."
    • addedInput schema / properties / challenge_id / description
      Added value: +"Canonical challenge id argument for the verify_direct_offer Direct Session operation."
    • addedInput schema / properties / offer_id / description
      Added value: +"Canonical offer id argument for the verify_direct_offer Direct Session operation."
  2. Added

TDQS

C2.6/5.0
Behavior3/5

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

Annotations already indicate this is a mutating, idempotent, non-destructive operation. The description adds the Authorization: Bearer header requirement, which is useful but does not disclose what side effects occur (e.g., state changes, external calls). It does not contradict the annotations.

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?

The description is very short and front-loaded, stating the operation in the first sentence and the auth requirement in the second. It avoids fluff, though it sacrifices detail for brevity.

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

Completeness2/5

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

For a tool with 4 required parameters and a complex domain (Direct Session operations), the description is severely lacking. It does not explain what a direct offer is, what verification entails, or how this fits into the broader workflow. The presence of an output schema helps but does not compensate for the absence of usage context.

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 the description does not need to explain parameters. However, the schema descriptions are largely tautological (e.g., 'Canonical offer id argument for the verify_direct_offer Direct Session operation'), providing little meaning. The description itself adds no parameter context, so the baseline 3 applies.

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

Purpose2/5

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

The description says 'Execute the canonical Direct Session verify_direct_offer operation,' which essentially restates the tool name without explaining what verifying a direct offer involves. It fails to distinguish this from sibling tools like approve_direct_session or create_direct_provider_verification_challenge.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It only mentions the authentication requirement, which is a prerequisite but not a usage condition. The sibling tools suggest various related operations, but the description offers no contextual differentiation.

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

All Conductor Relay MCP 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