Skip to main content
Glama

spatial_nearby

Read-onlyIdempotent

Find files related to a given file by identifying those topologically nearby in the project's import and call graph, ranked by recent activity. Helps navigate code dependencies efficiently.

Instructions

v3.1.0 M4: Files topologically near a given file, ranked by recent activity. Candidate set = BFS distance ≤ 2 over the indexer graph (imports + call edges) ∪ same-neighborhood files. Ranking: (1 / (1 + bfs_dist)) × log(1 + visit_count_30d). Falls back to neighborhood-only if the indexer graph isn't built.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kNoMax neighbors to return (default 5)
file_pathYesProject-relative file path
Behavior5/5

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

Adds rich behavioral context beyond annotations: BFS algorithm, fallback to neighborhood-only, ranking formula. No contradictions with annotations.

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?

Three sentences efficiently front-load purpose and detail algorithm, with no wasted words.

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?

Explains what is returned (ranked files) and algorithm, but lacks explicit output format. However, no output schema exists, so this is acceptable.

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 covers both parameters with descriptions (100% coverage). Description does not add significant parameter-level 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 clearly states it finds files topologically near a given file, ranked by recent activity, with specific algorithm details (BFS distance ≤ 2). This distinguishes it from siblings like spatial_neighborhood.

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?

Describes the candidate set and ranking, implying usage context, but does not explicitly state when not to use or compare to alternatives among spatial tools.

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/sachinshelke/codevira'

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