Skip to main content
Glama

find_nodes

Find nodes in your code graph by type, name, or file pattern. Supports partial and fuzzy matching for functions, classes, modules, and routes.

Instructions

Find nodes in the graph by type, name, or file pattern.

Use this when you need to:

  • Find all functions in a specific file: type="FUNCTION", file="src/api.js"

  • Find a class by name: type="CLASS", name="UserService"

  • List all HTTP routes: type="http:route"

  • Get all modules in a directory: type="MODULE", file="services/"

Returns semantic IDs that you can pass to get_context, get_node, get_neighbors, or find_guards.

Supports partial matches on name and file. When a name filter returns no exact matches, automatically falls back to fuzzy name matching using token similarity (CamelCase/snake_case aware). Use limit/offset for pagination.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
typeNoNode type (e.g., FUNCTION, CLASS, MODULE, PROPERTY_ACCESS)
nameNoNode name pattern
fileNoFile path pattern
limitNoMax results (default: 10, max: 500)
offsetNoSkip first N results (default: 0)
Behavior4/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 discloses partial matches, automatic fuzzy fallback, and pagination (limit/offset). It does not mention destructive actions or authentication, but the tool appears to be a safe read operation.

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 and well-structured with bullet points and examples. Every sentence adds value, and the information is efficiently 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?

The tool has 5 parameters and no output schema. The description explains what the tool does, how to use it, and what the output is (semantic IDs). It also covers pagination. Missing details about error handling or empty results are minor, so the description is fairly complete.

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?

Schema description coverage is 100%, so the schema already documents parameters. The description adds value by providing usage patterns (e.g., combining type and file) and explaining the fuzzy matching behavior for the name parameter, which goes beyond the schema.

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?

The description clearly states the tool finds nodes in a graph by type, name, or file pattern, with specific examples. It distinguishes from sibling tools like get_node (retrieves a specific node) and find_guards, by noting that it returns semantic IDs for use with other tools.

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?

The description provides explicit use cases with examples (e.g., find functions in a file, find a class by name). It does not explicitly state when not to use this tool or compare to alternatives, but the examples effectively guide the user.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Disentinel/grafema'

If you have feedback or need assistance with the MCP directory API, please join our Discord server