Skip to main content
Glama
Neko1313

graphlens-mcp

search

Search code by name, content, or meaning with literal matching and path globs. Optionally list all matching files exhaustively.

Instructions

Find code by NAME, CONTENT, or MEANING — the one way in (default limit 25). Returns graph nodes WITH their signatures (not dead text lines): often enough to answer without info(). Pass any node to relations/info. Use wherever you'd grep or search for a symbol; content hits fold into the enclosing symbol. text_matches = non-symbol hits. Content is matched LITERALLY (not regex) — write 'Request(' or 'getErrorMap(' as-is, no escaping needed. Scope with path_glob (e.g. 'tests/', '.ts', '!tests/' to exclude) — there is no file:/content: query syntax, so use this instead of guessing one. Test files are excluded by default unless you set path_glob yourself or the query says 'test' — pass path_glob='tests/' to search them on purpose. For 'list EVERY file that calls/imports X' — where the top-N node list could miss some — set exhaustive=true: returns every matching file path (no signatures), uncapped by the normal limit. If the response's note field is set, your exact text matched nothing — every node is a name/meaning guess, not a confirmed hit — simplify the query instead of repeating it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax nodes to return (clamped to 200)
queryYes
path_globNo
exhaustiveNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
viaNo
noteNo
countNo
errorNo
filesNo
nodesNo
indexingNo
truncatedNo
repeat_hintNo
text_matchesNo
resolver_statusNook
Behavior5/5

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

No annotations provided, so the description fully covers behavior: returns graph nodes with signatures, not dead text lines; text_matches for non-symbol hits; literal matching; note field indicates no exact matches; exhaustive mode returns all file paths without signatures; test file exclusion logic.

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?

The description is long but packed with valuable, non-redundant information. It is front-loaded with the main purpose and each sentence adds necessary detail. Slightly verbose but acceptable given the complexity.

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

Completeness5/5

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

Given the high complexity (4 parameters, multiple behaviors) and the presence of an output schema, the description covers all relevant aspects: parameter details, edge cases (note field, exhaustive, test files), and redirection to sibling tools. It is fully adequate for correct tool invocation.

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

Parameters5/5

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

Schema coverage is only 25% (only limit described), but the description compensates by detailing all parameters: limit (default 25, clamped to 200), query (search term), path_glob (scoping with examples and exclusion), exhaustive (boolean for full file listing). Adds significant meaning beyond 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 explicitly states the tool finds code by name, content, or meaning, and it is the primary search entry point, distinguishing it from the sibling tools 'info' and 'relations' which provide details and relationships.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides extensive usage guidance: use it like grep or search for symbols, how content hits fold, how to scope with path_glob (with examples), test file exclusion behavior, and the exhaustive option. It also implies when to use siblings after obtaining a node.

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/Neko1313/graphlens-mcp'

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