Skip to main content
Glama
Sign In
code-intel-mcp

code-intel-mcp

by dothinh115
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

find_references

Locate every occurrence of a function, class, or variable in your codebase with file and line details, enabling analysis of dependencies and call chains.

Instructions

Find all references to a symbol (function, class, variable, type) across a directory using ripgrep. Returns file, line, and matching text. Use to trace call chains and understand usage before modifying.

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": {
      "symbol": "<symbol>",
      "path": "<path>"
    },
    "name": "find_references"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesAbsolute path to a directory to search in
symbolYesSymbol name or regex pattern to search for
maxResultsNoMaximum results to return (default 50)
filePatternNoOptional glob to filter files (e.g. '*.ts', '*.vue')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It mentions using ripgrep and returning file/line/text, but does not disclose behavior like performance, .gitignore handling, or safety (read-only is implied but not explicit). With annotations absent, more detail would be beneficial.

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?

Two sentences, no fluff, each sentence earns its place: first defines action and method, second provides usage context. Perfectly concise and front-loaded.

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?

With no output schema, the description mentions 'Returns file, line, and matching text', covering the return format. It also gives a use case. Missing details like result truncation (maxResults) are minor; overall sufficient for a simple search tool with 4 parameters.

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%, so baseline is 3. The description does not add significant meaning beyond the schema; it reiterates 'symbol' and 'path' but does not elaborate on format or constraints. Falls into the typical baseline.

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

Purpose5/5

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

Description clearly states 'Find all references to a symbol across a directory using ripgrep', specifying verb and resource. It distinguishes from sibling tools like list_exports (exports) and file_outline (structure), leaving no ambiguity about what finds_references does.

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?

Includes explicit guidance: 'Use to trace call chains and understand usage before modifying', indicating when to use. However, it does not explicitly state when not to use or name alternatives, so a slight deduction applies.

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

Deploy Server

Other Tools