Skip to main content
Glama

get_search_status

Idempotent

Poll an existing search once to check its status or reread a completed run's dataset after a mapping fix or updated results, without starting a new paid run.

Instructions

Poll an existing search once. Set refresh_results=true to reread a completed run's dataset after a mapping fix or updated results. Never starts a new paid run.

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": {
      "search_id": "<search_id>"
    },
    "name": "get_search_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
search_idYes
refresh_resultsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.9/5.0
Behavior4/5

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

Adds genuinely useful context beyond the annotations: the cost model (no new paid run) and the fact that refresh_results re-reads an already-completed dataset. It does not conflict with readOnlyHint=false, since a refresh can regenerate output rather than purely read. Missing is any statement of what the poll returns (status values) or what happens when the search is still running.

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?

Three short sentences, front-loaded with the verb and scope, then the parameter trigger, then the safety guarantee. Nothing is redundant or padding.

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 definition should say what a poll yields (status states, dataset readiness) so the agent knows how to interpret the result and whether to poll again. The cost and refresh semantics are covered, but the return-side behavior and search_id provenance are left open.

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 0%, so the description must carry the burden. It explains refresh_results well (reread a completed run after a mapping fix), but search_id gets no meaning beyond "an existing search" — no hint on where it comes from or its format.

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?

"Poll an existing search once" names a specific verb (poll) and resource (an existing search), plus an explicit scope limit (once). "Never starts a new paid run" implicitly separates it from the search-creating siblings, though no sibling is named outright.

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?

The refresh_results condition is spelled out precisely: use it to reread a completed run's dataset after a mapping fix or updated results. It also gives a clear negative guardrail (never starts a new paid run), but it never says when to prefer this over get_scout_status or get_saved_results.

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