Skip to main content
Glama

how_is_project

Retrieves a project's status: current stage, milestone, merged and blocked tickets, active builders, repos, and last activity so you can assess progress.

Instructions

How one project is doing, as its row on the home page shows it: where it stands, the milestone it is on, tickets merged and blocked out of all, builders working, repos and when it last moved. project is its name or id.

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": "how_is_project"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.57.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. 'How one project is doing' strongly implies a read-only snapshot, and the enumerated fields make the returned content predictable, but nothing explicitly confirms there are no side effects, and error behavior for a nonexistent project id is unaddressed.

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?

One compact sentence with the resource statement front-loaded and the parameter clarification trailing. Everything earns its place except the somewhat opaque 'as its row on the home page shows it' framing, which spends words on a UI metaphor rather than on tool behavior.

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?

An output schema exists, yet the description still summarizes the payload so the agent can judge relevance without opening it, and the single identifier parameter is fully explained. For a one-parameter read tool this is nearly complete; only cross-tool routing guidance is missing.

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?

Schema description coverage is 0%, so the description must compensate for the single parameter — and it does: '`project` is its name or id' tells the agent both accepted identifier forms, which the bare string schema does not. No further resolution or format detail (e.g., partial matching) is given, keeping it just below a 5.

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 — a status readout for one project — and enumerates exactly what the readout contains (status, milestone, merged/blocked tickets, builders, repos, last activity). That is far more concrete than a restated name. It does not explicitly contrast itself with how_is_service or project_timeline, so it falls short of the 5 tier, but an agent can tell what it is.

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?

The phrase 'as its row on the home page shows it' implies a quick current-state snapshot rather than history or diagnosis, which gives implicit usage context. There is no explicit when-to-use/when-not guidance and no sibling is named as an alternative for, say, historical timelines or incident breakdowns.

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