Skip to main content
Glama

sp_prepare_search

Explicitly start or resume optional local embedding indexing in the background. Requires a locally configured worker. Default concept/word search needs no model and no preparation.

Instructions

Explicitly start or resume optional local embedding indexing in the background. Requires a locally configured worker. Default concept/word search needs no model and no preparation.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.5

TDQS

A4/5.0
Behavior4/5

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

Annotations only say readOnlyHint=false and non-destructive; the description adds the genuinely useful facts that this launches background work and depends on a locally configured worker. It omits how progress is observed or what happens if the worker is absent, which an agent would need before relying on it.

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?

Three short sentences, front-loaded with the action and followed by the prerequisite and the 'you probably don't need this' caveat. Slightly wordy openers ('Explicitly') but no filler sentences.

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?

For a no-parameter, no-output-schema tool the description covers purpose, prerequisite, and optionality adequately. The main gap is what to do after starting indexing (status checking), which is left unstated despite likely sibling support.

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 nothing for the description to disambiguate; baseline applies. No parameter claims are made that could conflict with the empty schema.

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?

States a specific verb ('start or resume') and a specific resource ('optional local embedding indexing'), and clarifies it runs in the background rather than performing a search itself. An agent can distinguish it from the sp_search_document / sp_read_document family, though it never names a sibling explicitly.

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?

Gives both the trigger condition ('requires a locally configured worker', indexing is optional) and an implicit exclusion ('default concept/word search needs no model and no preparation'), which tells the agent not to call this for ordinary lookups. It stops short of naming the concrete alternative tool or saying when to skip preparation entirely.

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