Skip to main content
Glama
alopez3006

snipara-mcp

by alopez3006

rlm_code_imports

Map code dependencies by listing imports for symbols/files or finding importers of a module.

Instructions

List imports for a code symbol or file, or find importers of a module.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qualified_nameNoRepo-qualified symbol name
symbol_keyNoStable symbol key for an exact match
file_pathNoResolve imports for a specific file path
directionNoout
include_file_nodesNoFor file_path lookups, include every scanned symbol in matched_targets instead of the compact module anchor
limitNo
Behavior2/5

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

No annotations provided; description lacks details on behavioral traits such as whether it modifies state, required permissions, or rate limits. Only states basic functionality.

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?

Single sentence that is concise, front-loaded, and directly states the purpose without extraneous information.

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

Completeness2/5

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

Despite having 6 parameters and no output schema, the description is minimal. It does not explain parameter relationships or the default direction, making it incomplete for confident usage.

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 67%, and the description adds no parameter-specific meaning beyond what's in the schema. Baseline score applies.

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 lists imports for a symbol or file, or finds importers of a module, distinguishing it from siblings like rlm_code_callers and rlm_code_neighbors.

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?

No explicit guidance on when to use this tool versus alternatives like rlm_code_callers or rlm_code_neighbors. Usage is implied but not compared.

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/alopez3006/snipara-mcp'

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