Skip to main content
Glama

setup_status

Check the progress of a repository setup operation by showing which tasks are completed, in progress, or pending.

Instructions

Check the progress of a repository setup operation. Shows which setup tasks are completed, in progress, or pending.

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

Input Schema

NameRequiredDescriptionDefault
projectDirYesAbsolute path to the project directory

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/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. It does disclose the return content (which tasks are completed, in progress, or pending) and the read-only framing of "Check/Shows," but it omits prerequisites (must a setup already be initialized?), behavior when no setup exists, and any permission or cost considerations.

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 with zero filler, front-loaded with the action and followed by the concrete output breakdown. Nothing is repeated from the schema or restated tautologically.

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 single-parameter read-only status tool with no output schema, the description adequately covers what the tool does and what it reports. The only meaningful omission is state/prerequisite context about when a setup operation exists to be checked.

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?

Only one parameter exists and the schema already documents it at 100% coverage ("Absolute path to the project directory"). The description adds no further meaning about projectDir — e.g., whether it must be an already-initialized project — so it neither compensates nor detracts.

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?

States a specific verb and resource ("Check the progress of a repository setup operation") and clarifies the payload with the completed/in-progress/pending breakdown. It does not explicitly distinguish itself from the setup_analyze or setup_init siblings, so an agent must infer that this one only observes rather than starts or analyzes setup.

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 implied by the name and the phrase "progress of a repository setup operation" — you call it to poll status. There is no explicit when-to-use/when-not-to-use guidance, no mention of whether setup_init must run first, and no reference to an alternative tool for starting or analyzing setup.

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