Skip to main content
Glama

mind_search

Read-onlyIdempotent

Search a repository's code index by symbol, path fragment, or phrase to get ranked file hits for locating relevant code.

Instructions

Search this repository's code index for a symbol, path or phrase; returns ranked file hits.

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": {
      "query": "<query>"
    },
    "name": "mind_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesSymbol, path fragment or phrase to find

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv3.62.0
    • changedInput schema / properties / query / description
      Previous value: -"search query or symbol"New value: +"Symbol, path fragment or phrase to find"
  2. First observedv0.1.0

TDQS

A3.6/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 and scope profile is fully covered. The description adds only the return shape ('ranked file hits'), which is modest added context beyond the structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One sentence, front-loaded with the verb and resource, ending with the return behavior. No filler or redundant restatement of the tool name.

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 single-parameter read-only search with full schema coverage and complete safe-operation annotations, the description covers purpose and return shape. It lacks result-count/pagination expectations, but nothing essential for correct invocation is missing.

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 coverage is 100% and the single parameter is fully documented in the schema. The description restates the same accepted query forms (symbol, path, phrase) without adding syntax, matching rules, or examples, so the baseline of 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?

States a specific verb (search) and resource (this repository's code index) and names the accepted query types (symbol, path, phrase). The sibling list contains mostly unrelated workflow tools, so no dedicated disambiguation is required, but it also doesn't contrast with any potentially overlapping search-like sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The phrase 'this repository's code index' implies the usage context, but there is no explicit when-to-use, when-not-to-use, or named alternative. An agent can infer it is the lookup tool for code, but the guidance is implied rather than stated.

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