Skip to main content
Glama

workbench_status

Read-only

Check local repositories, runtime entrypoints, active and stored cases, and available project checks; does not launch either engine.

Instructions

Check local repositories, runtime entrypoints, active cases, a page of stored cases and available project checks. Follow cases_page.next_offset for more cases. Does not launch either engine.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description's added value is the pagination behavior ('Follow cases_page.next_offset for more cases') and the non-execution scope boundary. It still doesn't describe the shape of each returned section, which matters since no output schema exists, keeping it short of a 5.

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 sentences, no filler: the first front-loads what is inspected, the second delivers the paging rule and the scope exclusion. Every clause carries information an agent needs.

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 description enumerates the sections returned and explains paging, which is reasonably complete for a read-only status tool lacking an output schema. Terms like 'runtime entrypoints', 'project checks', and 'either engine' are left undefined, so an agent cannot fully predict what it will receive.

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?

Schema description coverage is 0% for both parameters; the schema only supplies types, defaults, and min/max. The description conveys paging semantics through the mention of a page of stored cases and next_offset, but never ties that to the limit/offset parameters or warns about the 50-item cap.

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?

A specific verb ('Check') paired with an enumerated set of resources: local repositories, runtime entrypoints, active cases, stored cases, and project checks. An agent can see this is a status/overview tool rather than an action tool, and the closing 'Does not launch either engine' separates it from execution siblings like workbench_call or workbench_run_check.

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 scope statement plus the exclusion 'Does not launch either engine', which steers an agent away from expecting execution. However, there is no explicit guidance on when to prefer this over workbench_discover_tools or workbench_report, and no stated prerequisites.

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