django-chainsaw-mcp

Overview Schema Source Related Servers Score Discussions Admin

project_profile

Read-onlyIdempotent

Analyze a project directory to identify frameworks actually imported in its code, ignoring unused installed packages. Use this to determine which checks apply to your project.

Instructions

What this project is built on, without needing Django to boot.

Frameworks are counted by how many of the project's own files import
them, not by what is installed: a package sitting in the virtualenv that
nothing imports is a fact about the environment, not the code. A project
can be Django and FastAPI at once and both are reported.

Use it to find out which checks can say anything here.

Args:
    search_path: directory to scan. Defaults to the configured project.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`search_path`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.3Sep 9, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Behavior: Reasoning -- The description adds meaningful behavior beyond annotations: it avoids Django boot overhead, counts imports from the project's own files rather than installed packages, and can report multiple frameworks at once. Annotations already indicate read-only, idempotent, and non-destructive behavior; the description enriches this with methodology and runtime expectations.

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 front-loaded with the core purpose, followed by the important counting methodology, and ends with a usage pointer. The Args section is compact and every sentence adds distinct value without redundancy.

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 single optional parameter, the presence of an output schema, and strong annotations, the description covers purpose, when to use, parameter behavior, and key edge cases. There is no meaningful missing context for an agent to invoke it correctly.

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 coverage is 0%, so the description must compensate. It defines search_path as a directory to scan and states the default is the configured project, adding semantic meaning beyond the raw schema properties.

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's purpose: identifying what frameworks a project is built on, without needing Django to boot. It further distinguishes itself by explaining that frameworks are counted by project file imports, not installed packages, and that multiple frameworks can be reported simultaneously.

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 explicitly says 'Use it to find out which checks can say anything here,' giving a clear when-to-use context before running analysis checks. It does not explicitly name alternatives or state when not to use it, but the guidance is strong enough for an agent to select the tool appropriately.

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