Skip to main content
Glama
Sign In

Conductor Relay MCP

by io.github.Zman504
OverviewDiscussionsAdmin

Create Direct Provider Verification Challenge

create_direct_provider_verification_challenge
Idempotent

Execute the canonical Direct Session create_direct_provider_verification_challenge 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>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "create_direct_provider_verification_challenge"
  }
}

Input Schema

NameRequiredDescriptionDefault
offer_idYesCanonical offer id argument for the create_direct_provider_verification_challenge 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 create_direct_provider_verification_challenge 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. Changed1 schema field changed
    • addedInput schema / properties / offer_id / description
      Added value: +"Canonical offer id argument for the create_direct_provider_verification_challenge Direct Session operation."
  2. Added

TDQS

C2.7/5.0
Behavior4/5

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

The description adds the requirement for an Authorization: Bearer header, which is useful context beyond the annotations. Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the added auth detail fills a gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but the first sentence is filler that merely restates the tool name. The second sentence about the auth header is useful. It is concise but not optimally structured because the first sentence doesn't earn its place.

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?

The description lacks the core purpose and context needed to understand when or why to invoke this tool. Even with an output schema and good parameter schema, the missing functional description leaves the tool incomplete for an agent to use 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% and both parameters have descriptive JSON schema entries, so the description adds no additional parameter meaning. The baseline of 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 only says 'Execute the canonical Direct Session create_direct_provider_verification_challenge operation,' which tautologically restates the tool name without explaining what the operation does functionally. No information about creating a challenge or its role in the direct session lifecycle is provided.

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?

There is no guidance on when to use this tool versus alternatives like create_direct_signing_key_challenge or open_direct_session. The only usage hint is the auth header requirement, which is not enough to guide tool selection.

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