Skip to main content
Glama

setup_analyze

Detects repository setup freshness and missing configurations, showing required setup work before initialization.

Instructions

Analyze a repository to detect freshness (how much setup is needed) and identify missing configurations. Use this to understand what setup work is needed before running setup_init.

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": {
      "projectDir": "<projectDir>"
    },
    "name": "setup_analyze"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden; the word 'analyze' plus the read-only framing ('detect', 'identify') implies a non-mutating inspection, which is the key behavioral trait an agent needs. It does not state outright that nothing is written or whether the call is expensive/slow on large repos; with no output schema, the return shape is only loosely gestured at ('freshness', 'missing configurations').

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 sentences, no filler, with the purpose front-loaded and the calling condition second. Every clause earns its place by naming either an output or an ordering rule.

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 one-parameter analysis tool with a fully documented schema, the description covers purpose, outputs, and its place in the setup sequence. The remaining gap is that with no output schema an agent cannot know the shape or size of what comes back — only that it concerns freshness and missing configuration — and side-effect-free behavior is implied rather than stated.

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?

The single parameter projectDir is already fully documented in the schema (100% coverage, 'Absolute path to the project directory'), and the description adds nothing about it — no note on path expectations, relative-path rejection, or behavior when the directory lacks a repo. With schema coverage this high the baseline is 3, but the description supplies zero extra meaning, and 'a repository' vs. 'project directory' is a mildly ambiguous mapping.

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 opens with a specific verb and resource ('Analyze a repository') and names the two concrete outputs: setup freshness and missing configurations. It also explicitly positions itself relative to the setup_init sibling, so an agent can tell the two apart without opening either schema.

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?

It gives a clear usage rule — call this to learn what setup work is needed *before* running setup_init — which is an explicit sequencing constraint naming an alternative tool. It does not address when to prefer setup_status or when not to run analysis, so it stops short of full when/when-not coverage.

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