Skip to main content
Glama

read_search_status

Read-only

Check whether the search index is still building and see how many pages it holds, so you can confirm indexing is complete before running searches.

Instructions

Whether the search index is still building, and how many pages it holds.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "read_search_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered by structured data. The description adds useful behavioral context by disclosing the two pieces of state returned (build-in-progress and page count), but says nothing about cost, caching, or how a partially built index affects search results.

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?

A single short sentence with no padding, and the most important fact (index still building) is front-loaded. The sentence-fragment construction ('Whether ...') is slightly informal but costs no comprehension.

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 zero-parameter read tool the description is close to sufficient, and it does explain what is returned despite there being no output schema. It falls short on the operational question an agent actually faces: what to do with a 'still building' answer, or whether repeated polling is advisable.

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?

The tool takes zero parameters, so there is no parameter meaning for the description to supply; the baseline for a 0-param tool applies. Nothing in the description misrepresents the calling signature.

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 (the search index) and states exactly what information it reports: whether indexing is still in progress and how many pages are indexed. It is clearly distinguishable from read_search by subject matter, though it is phrased as a noun clause rather than an explicit verb, leaving the 'read' action implicit.

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 when-to-use guidance at all: nothing says to call this before or after read_search, nothing about polling behavior while the index builds, and no exclusions. The agent must infer that this is a diagnostic/health check adjacent to read_search purely from the name.

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