Skip to main content
Glama
importlens-mcp

importlens-mcp

by Matheos13

project_map

Summarizes a Python project's file count, modules, symbols, and lines to help coding agents understand repository shape before deeper analysis.

Instructions

Summarize the Python project: file count, modules, symbols, lines.

Call this first to understand the shape of the repo before drilling in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "project_map"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.2

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load. It implicitly signals a read-only summarization step, but never states whether the index must already be built (and hence whether reindex is a prerequisite), whether results are cached or fresh, or what happens on a non-Python repo. These are real gaps for a tool whose output the agent will rely on for orientation.

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?

Two short sentences, purpose first and the ordering instruction second, with no filler or repetition. Every sentence earns its place.

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 zero-parameter tool with a declared output schema, this is nearly complete: purpose, output contents, and invocation order are all covered, and return values needn't be explained. The only missing piece is a precondition — whether an index must exist, making reindex a required prior step.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline is 4. The listed outputs (file count, modules, symbols, lines) do usefully preview what the summary contains, though the output schema already covers that.

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 (summarize) and a specific resource (the Python project) plus the exact outputs — file count, modules, symbols, lines. That is enough to distinguish it from file_context and relevant_files, which drill into individual files. It stops short of a full 5 because the differentiation from siblings is only implied by 'before drilling in', not stated.

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?

'Call this first to understand the shape of the repo before drilling in' is a clear sequencing rule that tells the agent to run this before per-file tools. It does not name an explicit when-not condition or a named alternative, so it falls short of the 5 bar.

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

Deploy Server

Other Tools