Skip to main content
Glama

Requirements as checked

get_search_requirements
Read-onlyIdempotent

The requirements of a search as the results sheet shows them (how each criterion is checked, where the facts come from). [REST: GET /api/tasks/{id}/requirements]

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_requirements"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that — it discloses the response content (per-criterion checking logic and fact provenance) and the underlying REST route. It does not address failure modes (e.g., invalid or unknown task id) or result size, keeping this at an adequate rather than rich 3.

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?

One front-loaded sentence stating the returned content, plus a compact REST route annotation. Nothing is redundant, though the parenthetical could be tightened slightly for readability.

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 carries the burden of describing the return value; it gives a directional hint (per-criterion checks and data sources) but not the actual shape or fields. For a simple one-parameter read that is borderline sufficient, but an agent cannot fully anticipate the payload.

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% and the single task_id parameter is fully documented, including its pattern and where to obtain it (list_searches/create_search). The description adds no meaning about the id beyond what the schema already states, so the 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 the resource (a search's requirements) and qualifies the content — how each criterion is checked and where the facts come from — which is more specific than the bare title. The verb is only implicit ('as the results sheet shows them'), but an agent can still distinguish this from get_search or get_search_funnel by the criterion-level content it returns.

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?

No when-to-use guidance is given: the description never says whether this should be called before running a search, to audit an existing search, or as a follow-up to create_search. No alternative or exclusion is named, so selection relies entirely on the reader's inference from the tool name.

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