Skip to main content
Glama

sp_search_status

Read-only

Coverage and progress of the shared word/concept index and optional local embedding index. No model is started.

Instructions

Coverage and progress of the shared word/concept index and optional local embedding index. No model is started.

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": "sp_search_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.5

TDQS

B3.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds a genuine behavioral trait beyond them: 'No model is started', which tells the agent this call has no model-loading side effect or cost. It does not describe latency, cost, or what the status output contains, keeping it below a 5.

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?

Two short, front-loaded sentences with no filler; the resource is stated first and the no-model caveat follows. It is slightly clipped to the point of being a fragment, which costs a little clarity but not much.

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 parameters and no output schema, the description carries the burden of explaining what comes back, and 'coverage and progress' is only a rough sketch of the return shape. It is adequate for a trivial zero-argument status call but leaves the agent guessing about the fields and any progress semantics.

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 and the schema is an empty object, so there is no parameter meaning for the description to add. Per the zero-parameter baseline this sits at 4; nothing in the description misrepresents the argument surface.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description identifies the resource (the shared word/concept index and the optional local embedding index) and the aspect reported (coverage and progress), but it is a noun phrase with no verb and never distinguishes this from the several sibling status tools such as sp_check_status and sp_batch_check_status. An agent can guess it is a status/read tool, but not precisely what it returns versus those siblings.

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 explicit when-to-use guidance and no naming of alternatives among the many status siblings. The only implicit usage signal is 'No model is started', which hints that this is a cheap way to inspect index state, but the agent must infer that condition rather than being told it.

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