Skip to main content
Glama

Diagnose Project

project_diagnostic
Read-onlyIdempotent

Detect build, dependency, and configuration issues in a project without modifying files, helping you diagnose problems before making changes.

Instructions

Check a project for build, dependency and configuration problems without modifying it.

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_diagnostic"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectPathNoPath to the project directory (default: working directory)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotentHint=true, so 'without modifying it' largely restates structured data rather than adding to it. The genuinely additive part is the enumeration of what is inspected (build, dependency, configuration), but it says nothing about how long a check takes, whether it invokes a real build, or what a result looks like.

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?

One sentence, front-loaded with the action and the scope, with zero filler and the non-mutating guarantee placed at the end where it reads as a constraint rather than the point.

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 low-complexity, single-optional-parameter read-only tool with full annotation coverage, the description covers purpose and the non-mutating guarantee adequately. The only real gap is that with no output schema, an agent gets no hint about the shape of the diagnostic report (issues list, severity, pass/fail), which matters for deciding what to do with the result.

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 coverage is 100% with a single optional projectPath that already documents its default (working directory), so the schema carries the burden. The description adds no meaning about path resolution, whether relative or absolute paths are accepted, or what happens when the path is not a project.

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?

Names a specific verb (check) and resource (project) and narrows scope to three concrete problem classes: build, dependency and configuration. This separates it reasonably well from siblings like analyze_code or check_security, though it never explicitly says how it differs from those.

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?

Usage is only implied: an agent can infer this is a pre-flight/sanity-check step before building or fixing. There is no explicit when-to-use statement, no exclusion (e.g. 'use check_security for vulnerabilities'), and no mention of prerequisites such as the project needing to exist on disk.

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