Skip to main content
Glama

group_run_cancel

Cancel every still-active lane of a group run.

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": {
      "group_run_id": "<group_run_id>"
    },
    "name": "group_run_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_run_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does add real behavioral content beyond the name: cancellation is bulk (all lanes) and selective (only still-active ones), which suggests partial idempotency. It omits irreversibility, permission requirements, partial-failure behavior, and what is returned, which matters for a destructive operation.

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 no filler; scope and target are stated immediately. It is arguably over-lean for a destructive bulk operation, but every word earns its place.

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

Completeness2/5

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

For a destructive bulk mutation with no annotations, no output schema, and an undocumented identifier, the definition leaves too much unsaid: reversibility, effects on completed lanes, error semantics, and the response are all absent. The agent can guess the intent but not the consequences of calling it.

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?

There is one required parameter with 0% schema description coverage, so the description must compensate. 'Of a group run' implies group_run_id identifies the target run, but it says nothing about expected format, whether the ID comes from group_run_list/group_run_start, or what happens if the ID is unknown.

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 ('Cancel') and resource ('every still-active lane of a group run'), which is more precise than the name alone because it discloses bulk scope and that only active lanes are affected. It does not, however, contrast itself with the closely named sibling run_cancel, so an agent must infer the distinction from the name gap.

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?

The phrase 'every still-active lane' implies the appropriate case (stopping an in-flight multi-lane group run) and hints that finished lanes are untouched, but there is no explicit when-to-use, when-not-to-use, or pointer to run_cancel for single-run cancellation. Usage is implied rather than stated.

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