Skip to main content
Glama

ask

Send a task to another AI agent session and wait for its result; if no result arrives within the timeout, returns a pending task ID for later retrieval.

Instructions

Send a task and wait for its result (default 110 s, max 300). Returns pending with a task id if none came.

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

Input Schema

NameRequiredDescriptionDefault
toYes
taskYes
timeout_sNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose two genuinely useful traits: the default 110 s timeout with a 300 s ceiling, and the fact that a non-completion returns a pending status with a task id rather than blocking indefinitely or erroring. It omits what the caller should do with that task id and whether the task still executes after a timeout, which leaves the most consequential behavior ambiguous.

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

Conciseness5/5

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

Two short sentences, both load-bearing, with the blocking contract and its timeout bounds front-loaded. Nothing is padded or repeated from the schema.

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 3-parameter tool with no annotations and no output schema, the definition covers call mechanics (timeout, blocking, pending fallback) but leaves the return shape and the follow-up path for a pending task unexplained. An agent knows how to call it but not how to complete the round trip.

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 all three parameters depend on the prose. The timeout_s parameter is well served (default 110 s, max 300), and "task" is loosely implied, but "to" is completely uncharacterized despite being required — an agent cannot tell whether it takes a peer name, an id, or a room.

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?

"Send a task and wait for its result" names a concrete action and its blocking semantics, which distinguishes it from the fire-and-forget siblings like send and wait. It stops short of 5 because the target of "to" (peer, room, agent id?) is never characterized, so the resource side of the verb+resource pair is only half specified.

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 explicit when-to-use guidance and no sibling is named as an alternative. The phrase "wait for its result" implies this is the synchronous counterpart to send, but the agent must infer that routing decision rather than read it.

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

Deploy Server

Other Tools