Skip to main content
Glama

analyze_project

Read-onlyIdempotent

Inspect a project's source inventory, framework, scripts, route evidence, assets, and branding to build bounded evidence for analysis.

Instructions

Inspect bounded source inventory, framework, scripts, route evidence, assets and branding.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "analyze_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds only the word 'bounded' as evidence of scan scope, without saying what the bounds are, what gets skipped, or whether the operation is costly on large repos.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler, and the scope qualifier 'bounded' sits early. The trailing noun list is dense but each item is informative.

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?

An output schema exists, so return values need no explanation, but for a one-parameter analysis tool the definition leaves the sole input undefined and gives no routing guidance among the many analyze_*/inspect_* siblings. That is not sufficient for confident invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is one required parameter, 'project', with 0% schema description coverage, so the description carries the full burden — yet it never explains what form 'project' takes (path, name, or ID) or whether it must exist locally first. The facet list describes output content, not the input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a verb ('Inspect') and enumerates the facets examined (source inventory, framework, scripts, route evidence, assets, branding), so the general intent is graspable. But 'inspect' is vague about what the tool actually produces, and the listed facets overlap directly with siblings like discover_routes, detect_brand_identity, and inspect_media_assets with no differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this tool, no prerequisites, and no mention of alternatives, despite several sibling analyzers covering adjacent territory. The agent must infer positioning from the name alone.

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