Skip to main content
Glama

grid_status

Read-only

Displays Nightshift Grid capacity: worker IDs, capability tiers, states, models, live tok/s, completed or preempted counts, task queue depth by state, and recent job progress.

Instructions

Show Nightshift Grid capacity: each worker's id, capability tier (1 embeddings, 2 JSON extraction, 3 heavy), state, model, live tok/s and completed/preempted counts; task queue depth by state; and the most recent jobs with progress.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and locality are covered without the description's help. The description adds that the metrics are 'live' and that jobs shown are the 'most recent', which is mild behavioral context, but it says nothing about freshness windows, snapshot staleness, or cost of polling.

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 front-loaded sentence with the resource named first and details following, which is efficient. However, the long enumeration of returned fields partially duplicates what the existing output schema already declares, so a few of those clauses do not fully earn their place.

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

Completeness5/5

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

Zero parameters, read-only annotations, and an output schema that defines return values — the description covers the one thing the structured data cannot: what this snapshot is for and what it summarizes. Nothing an agent needs in order to invoke it correctly 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?

The tool takes zero parameters, so the schema baseline of 4 applies; there is nothing for the description to disambiguate. It correctly spends no words on arguments.

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 gives a specific verb ('Show') and a precise resource ('Nightshift Grid capacity'), then enumerates the exact contents: worker ids, capability tiers with their numeric meanings, state, model, live tok/s, completed/preempted counts, queue depth by state, and recent jobs. An agent knows immediately this is a read-only observability snapshot, which is clearly distinct from the ingestion/query/dispatch siblings.

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 only implied — the agent can infer this is the tool for inspecting grid health, but there is no explicit statement of when to reach for it (e.g., before dispatching work to check capacity) or when another tool is preferable. No prerequisites, no exclusions.

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