Skip to main content
Glama

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

bridge_create_ask

Create a bridged elicitation ask. Requires account_token. Trial and plan-included asks run here; paid asks collect over the HTTP x402 surface.

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": {
      "account_token": "<account_token>",
      "session_id": "<session_id>",
      "era": "<era>",
      "params": "<params>"
    },
    "name": "bridge_create_ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
eraYes
paramsYes
session_idYes
account_tokenYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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, yet it only discloses that account_token is required and how trial/paid routing works. It says nothing about what creating an ask actually does, whether it is mutating or idempotent, what session_id binds to, or what the call returns.

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?

Two short sentences with the core action front-loaded and no filler. The structure is efficient, though the brevity leaves important content unstated rather than being genuinely complete.

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?

This is a relatively complex tool — four required parameters including a nested object, no annotations, no output schema — and the description explains only auth and trial/paid routing. An agent would still not know what to put in era or params, or what happens after creation.

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 coverage is 0%, so the description must compensate for four required parameters, but it only mentions account_token as required. The meanings of era, session_id, and the nested params object are entirely undocumented in both the schema and the description.

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?

States a specific verb ('Create') and resource ('bridged elicitation ask'), so the basic operation is identifiable. However, 'bridged elicitation ask' is domain jargon, and the description does nothing to distinguish this from the sibling tools bridge_poll and bridge_unsupported_error.

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

Usage Guidelines4/5

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

Provides a real routing rule: trial and plan-included asks belong here, while paid asks are collected over the HTTP x402 surface. That is an explicit when-to-use and when-not, though the alternative is an external surface rather than a named sibling tool.

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