Skip to main content
Glama

A search: state and next step

get_search
Read-onlyIdempotent

One search: status, progress, counts, credits charged, the estimate (price examples), what to do next (next); for a search that asks about a higher price, the question (ask). detail=spec adds the requirements as the review screen shows them (criteria with ids, pains, counter-signals, the search method and its options, veins); detail=full adds the brief in full. Poll it while a search compiles or runs. [REST: GET /api/tasks/{id} (+ GET /api/tasks while it runs, GET /api/tasks/{id}/snapshot while it asks)]

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": {
      "task_id": "<task_id>"
    },
    "name": "get_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
detailNosummary
task_idYesThe search id (task id), e.g. from list_searches or create_search.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, non-open-world), and the description still adds real behavior: credits charged are surfaced, a price estimate with examples is returned, and a search may enter an `ask` state requiring a user answer, which explains why polling is appropriate. It does not mention pagination or rate limits, but the state machine disclosure is substantive.

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?

The payload enumeration is front-loaded, and the bracketed REST note is compact and useful rather than filler. The prose is dense and semi-parenthetical, but nearly every clause carries distinct information an agent would otherwise have to discover by calling.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/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 carries the burden of return-value disclosure and does so by listing the fields and states returned, plus the `ask` branch. For a two-parameter read tool with annotations already covering safety, the only missing piece is confirmation of how a completed vs. failed search is represented.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage sits at 50%, with `task_id` documented in-schema and `detail` documented only by its enum values. The description compensates by defining what detail=spec adds (criteria with ids, pains, counter-signals, search method and options, veins) and what detail=full adds (the brief), which is meaning the schema alone does not convey.

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 resource and enumerates the concrete payload it returns — status, progress, counts, credits charged, the estimate, the `next` step, and the `ask` question — so an agent knows exactly what it is retrieving. It stops short of 5 because it never contrasts itself with adjacent readers (e.g., the requirements-specific or funnel-specific lookups), even though detail=spec is said to surface requirements content.

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?

"Poll it while a search compiles or runs" gives a clear temporal condition for invocation, and the detail levels imply when to escalate from summary to spec to full. There is no explicit when-not guidance or named alternative for one-off requirement fetches, so it lands at clear-context-but-no-exclusions.

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