Skip to main content
Glama

Pause, resume or cancel research

spur_control_data_job
Destructive

Pause/cancel a job, or resume it with an optional revised budget. Resume can spend credits and requires confirm=true. Preserves completed results.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, openWorldHint=true, and non-idempotent, so the safety bar is partly met. The description adds meaningful context beyond them: resume can consume credits, resume demands an explicit confirm, and completed results survive the operation. It does not clarify whether cancel is irreversible or whether a paused job can always be resumed later, which is the main remaining behavioral gap.

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?

Three short sentences, zero filler, with the actions front-loaded and the credit/confirm risk stated before the reassuring note about preserving results. 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.

Completeness4/5

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

With no output schema, the description correctly focuses on behavior: what the actions do, the cost/confirm gate on resume, and the fate of completed results. Annotations carry the destructiveness profile, so little is missing; only the irreversibility of cancel and post-pause recoverability are left unstated.

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 100%, so the confirm and budget_limit_micros semantics are already documented in the schema itself. The description does add the useful framing that the budget is an 'optional revised budget' applicable to resume, but it adds no units, bounds, or effect details beyond that, so baseline 3 applies.

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 description uses specific verbs and a clear resource ('Pause/cancel a job, or resume it') and enumerates all three supported actions, so an agent can immediately tell this is the lifecycle-control tool for a data job. It implicitly separates itself from read/inspect siblings like spur_get_data_job and from launch siblings like spur_run_data_job, though it never names them explicitly.

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 gives a concrete precondition for the riskiest branch ('Resume can spend credits and requires confirm=true'), which is genuine when-to-use guidance for resume. However, it offers no guidance on choosing between pause, cancel, and resume, no mention of when cancel is preferred over pause, and no pointer to inspection tools before acting.

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