Skip to main content
Glama

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

bridge_unsupported_error

The per-era unsupported-ask error this product replaces (-32601 for 2025 eras, -32021 for 2026-07).

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": {
      "era": "<era>"
    },
    "name": "bridge_unsupported_error"
  }
}

Input Schema

NameRequiredDescriptionDefault
eraYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the full burden, yet it never says whether the tool emits an error object, throws, or returns a code, nor what side effects or auth needs apply. The era-to-code mapping (-32601 vs -32021) is useful context, but the core behavior of the call is left unstated.

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?

It is short with no wasted words, but it leads with a backward-looking clause about what the product replaces rather than a front-loaded statement of the action. The size is appropriate only because the content is incomplete.

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

Completeness3/5

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

For a single-parameter bridge tool with no annotations, no output schema, and 0% schema description coverage, the description should at minimum state the action and the return behavior. It supplies useful era/code domain knowledge but leaves the fundamental call behavior ambiguous.

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 0% and the single required 'era' parameter is undocumented in the schema. The description partially compensates by implying that era selects between error codes, naming '2025 eras' and '2026-07' as values, but does not give the accepted string format or a full value list.

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 sentence is a noun phrase describing a legacy error code, not a statement of what the tool does. An agent cannot tell whether it returns a code, raises an error, or formats a message, and there is no differentiation from bridge_create_ask or bridge_poll beyond the word 'unsupported'.

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 when-to-use guidance, no mention of the sibling tools, and no statement of preconditions or when this should be avoided. The only hint is that the tool relates to unsupported asks, which the agent must infer from the name.

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