Skip to main content
Glama

Find code in the codebase graph

graph_find
Read-only

Search a local codebase graph for functions, methods, and classes by name; returns IDs, file paths, line numbers, and summaries, building the graph first if missing.

Instructions

Search the codebase graph for functions, methods and classes by name. Each result has its id, file, line and plain-English summary when one exists. Builds the graph first if the repository has none (Python, TypeScript, JavaScript). Returns JSON. Read-only and local.

Works without SKYLOS_API_KEY and has no daily limit: it reads the repository on this machine and sends nothing to Skylos Cloud.

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

Input Schema

NameRequiredDescriptionDefault
pathNoProject directory. A relative path resolves against the MCP server's working directory..
queryYesPart of a function, method, class or file name
include_testsNoAlso search test code

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv5.6.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, yet the description still adds real context: it builds the graph first when the repository has none (a notable latency and side-effect behavior), returns JSON, and requires no API key or daily quota because it stays local. The only missing piece is how long that initial build takes.

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?

Two short paragraphs, front-loaded with what the tool does and the result shape before the operational caveats. The second paragraph is slightly promotional in tone but each sentence carries information an agent would use.

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 three-parameter search tool with a full schema, annotations and an output schema, the description covers the important extras: graph auto-build, supported languages, and the local/no-quota behavior. Only the cost of the initial build and the exact matching rules are left unstated.

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 description coverage is 100%, so all three parameters are already documented in structured fields. The description restates the query scope but actually narrows it, listing functions, methods and classes while the schema also covers file names, adding no syntax or matching-behavior detail beyond the 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 gives a specific verb and resource: "Search the codebase graph for functions, methods and classes by name." That is enough to separate it from analysis tools like analyze or security_scan, but it never contrasts itself with the closer siblings graph_show, graph_describe, or graph_relevant, so an agent must infer the difference from the names.

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 "by name" phrasing implies the lookup use case and the supported languages are named, but there is no explicit when-to-use or when-not guidance and no named alternative for structural or impact questions. Usage 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.