Skip to main content
Glama

Ask

ask

Order window. need is required. status is answered only when a BotThru tool ran, routed when Workers AI wrote a pointer and the task was not done, unsupported when the need was only logged. Do not send secrets or personal data.

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": {
      "need": "<need>"
    },
    "name": "ask"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesWhat you need. Do not include secrets or personal data.
agentNoOptional name of the calling agent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.2/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 burden, and it does disclose something valuable: the outcome states (answered / routed / unsupported) and a privacy constraint against sending secrets or personal data. However, those states are defined in opaque internal jargon ("BotThru tool ran", "Workers AI wrote a pointer") that an agent cannot reliably act on, and nothing is said about required permissions, latency, or what the caller should do next per state.

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

Conciseness2/5

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

It is short, but it is not front-loaded with purpose — the useful information is buried behind a cryptic two-word opener, and the status clause is a dense run-on of internal terminology. Brevity here reflects under-specification rather than efficiency.

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?

There is no output schema, so the description should explain what calling the tool returns; it gestures at a status field but never says where status appears or what a caller should do with each value. For a submission tool with no annotations, that leaves an agent unable to predict the response or the side effects of calling it.

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 description coverage is 100%, so both parameters are already documented; the description's "need is required" and privacy warning simply repeat the schema. No added meaning about format, length, or examples is provided, 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 opening fragment "Order window" states nothing about what the tool does, and the rest of the description is dominated by status-code semantics rather than a verb+resource. Only "need is required" hints that this submits a request/need, which an agent must infer.

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 the many sibling lookups (whoami, time, check_url, etc.), nor when not to. The only conditional content concerns output statuses, not invocation conditions.

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