Skip to main content
Glama

repo_search

Read-onlyIdempotent

Search indexed file paths and symbols by query to locate code definitions and relevant files in a local codebase.

Instructions

Search indexed file paths and symbols.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.6

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so safety is fully covered without the description. The one added signal is the word "indexed," hinting that results come from a pre-built index and may be stale, but match semantics, ranking, and result shape are all undisclosed.

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 front-loaded sentence with zero filler or redundancy. Its brevity is admirable structurally, though it edges toward under-specification for a tool with two undocumented parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, no parameter descriptions, and a five-word description, an agent cannot know query syntax, the default page size, whether results are ranked, or what a hit looks like. It is adequate only for the crudest 'grep for a filename' invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description carries the full burden for both parameters. Saying it searches "file paths and symbols" gives partial meaning to `query` (what it matches against), but says nothing about syntax (substring, regex, fuzzy), and `limit` is completely unaddressed — no default, no maximum, no effect on truncation.

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 verb ("Search") and a specific resource set ("indexed file paths and symbols"), which is enough to distinguish it from memory-oriented siblings like repo_team_memory_search. It stops short of explicitly contrasting itself with code-understanding siblings such as repo_architecture or repo_explain, so the differentiation is implicit rather than stated.

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, no stated prerequisites (e.g., that an index must exist), and no mention of when a different tool would be better. An agent must infer from the name alone that this is the lookup step before calling repo_explain or repo_architecture.

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