Skip to main content
Glama

project_status

Read-only

Retrieves the project overview first: PROJECT.md intent, blocks, decisions, open items, plus per-circuit counts, unplaced/unrouted items, errors, warnings, and recent changes.

Instructions

Call this first in every task: PROJECT.md (intent, blocks, last decisions, open items), then per circuit file its counts, unplaced, unrouted, errors, warnings and last changes.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered without the description. The description adds value by disclosing the shape of what comes back (PROJECT.md fields plus per-circuit counts/errors/warnings), but says nothing about cost, size limits, or whether missing files yield errors. Useful additional context, but not rich behavioral disclosure.

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 sentence with the most important instruction front-loaded ('call this first in every task'). The trailing enumeration of per-circuit fields is a bit dense and run-on but every item carries information an agent would otherwise have to discover by calling the tool.

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?

With no input schema to explain and no output schema provided, the description shoulders the burden of describing returns and does so with a concrete field list. It is nearly complete for a zero-argument status tool; only the absence of failure/empty-project behavior keeps it from a 5.

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?

The tool takes zero parameters, so parameter semantics are inherently satisfied and the baseline is 4. The description instead spends its words on the returned sections, which is the right allocation for a no-argument tool.

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?

The description makes clear this returns the project status document (intent, blocks, last decisions, open items) plus per-circuit diagnostics (counts, unplaced, unrouted, errors, warnings, last changes). The action verb is implicit ('call this first') rather than stated, but the content is concrete enough that an agent knows it is a read of overall project state. It does not explicitly distinguish itself from siblings like board_summary or circuit_summary, which is the only gap.

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?

Gives strong, explicit ordering guidance: 'Call this first in every task.' That is a clear when-to-use directive an agent can act on immediately. There are no exclusions or named alternatives for when a narrower summary tool might be preferable, so it stops short of full routing guidance.

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