code-index-mcp

Overview Schema Source Related Servers Discussions Admin

search_symbol

Find symbol definitions like functions, classes, and methods by name. Supports exact and substring matching with optional index selection.

Instructions

Find symbol definitions (function/class/method/record/...) by name.

Use to jump to where something is DEFINED. Set exact=true for an exact name match, otherwise substring matching is used. service selects the index.

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

Input Schema

Name	Required	Description	Default
`name`	Yes
`limit`	No
`exact`	No
`service`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 23, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It does not mention whether the operation is read-only, requires authentication, or has any side effects. The explanation is limited to parameter effects.

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?

The description is concise (two sentences plus a line of parameter notes), front-loaded with purpose, and contains no redundant information.

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?

Covers purpose, parameters, and basic usage. Missing behavioral context like error cases, return format (though output schema exists), or prerequisites. Adequate but not thorough.

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?

With 0% schema description coverage, the description explains all three non-required parameters (limit, exact, service) and their defaults or meanings, adding value beyond the raw 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?

The description clearly states the tool's purpose ('Find symbol definitions') with a specific verb and resource, and gives examples of symbol types. It implies differentiation from siblings by focusing on definitions rather than text search, but does not explicitly name alternatives.

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?

Provides basic guidance (use to jump to definitions, explains exact and service parameters) but lacks explicit when-not-to-use or alternative tool suggestions. Siblings like search_text and file_symbols are not addressed.

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

Deploy Server