Skip to main content
Glama

Read, resume or cancel a column run

spur_control_table_run
Destructive

Get progress/changed rows, resume under a credit ceiling, or cancel. Resume requires approval and is safe to retry without double charging.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and openWorldHint=true, and the description adds genuinely new context: resume consumes credits under a ceiling and is safe to retry without double charging. The approval requirement is behaviorally important and not derivable from annotations alone. There is mild tension between 'safe to retry' and idempotentHint=false, but the claim is scoped to billing rather than to the tool's overall effect, so it reads as a nuance rather than a contradiction.

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 short sentences, front-loaded with the action set and followed by the one non-obvious constraint (approval plus billing safety). No filler, nothing repeated from the title or schema.

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 a multi-action, destructive, credit-spending tool with no output schema, the description covers the risky paths (resume approval, billing) and hints at what get returns ('progress/changed rows'). It stops short of saying what cancel does to in-flight work or what state a run is left in, which would matter before an agent invokes a destructive action.

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 coverage is reported at 100%, so baseline would be 3, but the description adds real meaning the schema lacks: credit_limit is a spending ceiling for resume, and the approval gate governs when confirm may be set. That is semantic value beyond the min/max bounds and const in the schema.

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?

The title and first sentence give a specific verb set (get, resume, cancel) against a specific resource (a column run), and enumerate the three actions so an agent knows exactly what the tool can do. It does not explicitly contrast itself with the run-starting sibling spur_run_table_column, which is the main residual ambiguity.

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?

It states one hard prerequisite ('Resume requires approval'), which is real when-to-use guidance, and the action enum implies the get/cancel paths. However, it never says when to prefer get over cancel, or how this differs from spur_run_table_column or spur_control_data_job, leaving the highest-stakes routing decision (start a new run vs. control an existing one) to inference.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources