Skip to main content
Glama

status

View live progress on who is doing what, active claims, open blockers, and latest events for multi-agent coordination.

Instructions

Live progress: who is doing what, claims, open blockers, latest events.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.11

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. 'Live progress' implies a read-only, current-state snapshot, and 'open blockers' implies filtering to unresolved items, which is useful behavioral context. However, it never states that the call is side-effect free, nor how 'live' is bounded in time — an important ambiguity for a zero-parameter call.

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 compact line with no filler, and the most important framing ('Live progress') is front-loaded. It reads as a fragment rather than a sentence, which costs a little polish but wastes nothing.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is simple (zero params, output schema present), so the description needn't explain return values, and it does not try to. What is missing is scope and routing: the agent cannot tell which subsystem's status this is or when to prefer it over the event-oriented siblings.

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 the schema baseline of 4 applies and there is nothing for the description to compensate for. The mention of distinct content categories (claims, blockers, events) is a minor bonus for interpreting the returned sections.

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 enumerates the content the tool surfaces (progress, claims, blockers, latest events), which gives a reasonable idea of what a call returns. But it is written as a noun fragment with no verb and no object of scope — 'live progress' of what system, team, or project is never stated. It is distinguishable from mutation siblings like claim or rule_add, but overlaps unaddressed with news and log.

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?

No when-to-use guidance is given, and no alternative is named. The listed content ('latest events') overlaps conceptually with the sibling news and log tools, and the description never clarifies which to call for recent-activity questions. The agent must guess.

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

Deploy Server

Other Tools