Skip to main content
Glama

Elicitation Bridge: out-of-band answer channel for unsupported clients

bridge_poll

Poll a bridged ask for its era-shaped result (account token + ask token + session binding required; same operator-isolation gate as the HTTP poll).

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": {
      "ask_id": "<ask_id>",
      "token": "<token>",
      "account_token": "<account_token>",
      "session_id": "<session_id>"
    },
    "name": "bridge_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenYes
ask_idYes
session_idYes
account_tokenYes
request_stateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / account_token
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / request_state
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / session_id
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "ask_id",
      -  "token"
      -]New value: +[
      +  "ask_id",
      +  "token",
      +  "account_token",
      +  "session_id"
      +]
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It discloses required tokens and an operator-isolation gate, but omits core poll behavior such as whether it blocks, what happens while the ask is pending, rate limits, idempotency, or error handling.

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 definition is a single front-loaded sentence with no obvious filler. It is efficient, though the jargon terms 'era-shaped' and 'operator-isolation gate' make it less immediately clear than a more plain-language phrasing would.

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 five-parameter tool with no annotations, no output schema, and 0% schema description coverage, the description is too thin. It leaves request_state undefined and does not explain the result shape, pending-state behavior, or error conditions an agent would need to invoke and interpret the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must explain all five parameters. It maps 'account token', 'ask token', and 'session binding' to account_token, token, and session_id, and implies ask_id via 'bridged ask', but it never explains request_state or any token format expectations.

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 gives a clear verb and resource: 'Poll a bridged ask for its result.' It distinguishes the action from bridge_create_ask by implying retrieval rather than creation. However, 'era-shaped result' is jargon that reduces precision, and no sibling is explicitly named.

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?

The description implies polling an existing bridged ask but does not state when to use this tool instead of bridge_create_ask or bridge_unsupported_error. It also gives no guidance on retry timing, pending states, or when polling is appropriate.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources