Skip to main content
Glama

workbench_run_check

Run a configured project check by exact name and capture exit codes, bounded logs, parsed XCTest/TAP results, and compiler diagnostics; timeouts or cancellations never pass.

Instructions

Execute one configured or currently declared project check by its exact discovered name. Requires case allow_execution=true. Captures exit code, bounded original logs, parsed XCTest/TAP results and compiler diagnostics; timeouts/cancellation are never reported as passing.

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": {
      "case_id": "<case_id>",
      "check": "<check>"
    },
    "name": "workbench_run_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
checkYes
case_idYes
timeout_msNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior4/5

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

Beyond the annotations (readOnlyHint=false, destructiveHint=false, openWorldHint=true), the description discloses what the call produces — exit code, bounded logs, parsed XCTest/TAP results, compiler diagnostics — and a meaningful correctness guarantee that timeouts and cancellation are never reported as passing. It does not describe how long executions behave or what happens when logs are truncated.

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?

Two front-loaded sentences with no filler: the action and its precondition come first, the result contract second. The clause-stacked second sentence ('bounded original logs, parsed XCTest/TAP results and compiler diagnostics') is dense but each item carries information.

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?

For an execution tool with no output schema, the description does the heavy lifting by describing the returned artifacts and the non-passing semantics of timeouts. Remaining gaps are the timeout parameter and any guidance on long-running or failing executions.

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?

With 0% schema description coverage, the description must carry parameter meaning: it adds real semantics for 'check' (must be an exact, discovered name) and implies case scoping via the allow_execution precondition. However, 'timeout_ms' is never mentioned and 'case_id' is only indirectly implied, leaving two of three parameters semantically thin.

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: execute one configured or currently declared project check, keyed by its exact discovered name. It clearly separates this from generic command execution (workbench_call) by scoping to project checks, though it does not name any sibling explicitly.

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?

"Requires case allow_execution=true" gives a concrete precondition an agent must verify before calling, and "by its exact discovered name" implies checks must be discovered first rather than invented. It stops short of naming exclusions or pointing to alternatives for arbitrary command execution.

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