Skip to main content
Glama

Poll a research run

research_status
Read-only

Poll a started research run with its handle to check its state or retrieve the answer once available.

Instructions

Poll a run research started: its state, or the answer once it has one. Free, about a second.

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": {
      "handle": "<handle>"
    },
    "name": "research_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesThe handle a `research` call handed back.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.13.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely new behavioral context: cost ('Free') and latency ('about a second'), plus the fact that a result may not yet exist ('once it has one'). It stops short of describing what the possible states are or what a not-yet-ready response looks like.

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 clauses, front-loaded with the action and resource, then the return value, then the cost/latency note. Every phrase carries information and nothing is padded.

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?

With no output schema, the description must carry the return-value burden, and it only gestures at it ('its state, or the answer'). For a polling tool, the enumeration of possible states and the signal for 'still running, keep polling' versus 'finished' or 'failed' would materially change agent behavior, and that is missing.

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?

There is one parameter with 100% schema description coverage, so the schema already explains that `handle` is 'The handle a `research` call handed back.' The description restates that same linkage ('a run `research` started') without adding format, validity, or lifetime details, so baseline 3 applies.

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 names a specific verb and resource — 'Poll a run `research` started' — and clarifies the return payload ('its state, or the answer once it has one'). It clearly distinguishes itself from the `research` sibling that initiates the run, though it does not explicitly distinguish itself from other *_status siblings like browse_status or budget_status.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: the phrase 'a run `research` started' tells the agent this follows a `research` call, and 'Free, about a second' signals it is cheap enough to call repeatedly. However, there is no explicit guidance on polling cadence, how many times to poll, or when to stop versus giving up.

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