Skip to main content
Glama
Sign In

mcp-server

by io.alterlab
OverviewDiscussionsAdmin

Cancel Run (beta)

alterlab_run_cancel
Idempotent

Stop the pending steps of a run (beta feature) and refund the unused part of the reserved budget. Steps already in flight settle first.

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": {
      "run_id": "<run_id>"
    },
    "name": "alterlab_run_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
run_idYesRun id returned by alterlab_run_create

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations by disclosing the partial-effect semantics: only pending steps are stopped, already in-flight steps settle first, and the unused reserved budget is refunded. This explains why destructiveHint=false is still a sensible label for a stop operation. It stops short of covering permissions, what a caller gets back (status or refund amount), and the caveats implied by the beta label.

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 with the primary action and its conditional behavior front-loaded, and zero redundant wording. The beta caveat is attached inline rather than padding the definition.

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 one-parameter lifecycle tool with no output schema and annotations covering safety and idempotency, the description covers the essential behavior, including the non-obvious settlement and refund semantics. Only minor gaps remain, such as error behavior for invalid or already-completed run ids.

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%, and the single run_id parameter is fully documented in the schema as the id returned by alterlab_run_create. The description adds no further meaning about the parameter (e.g. whether an unknown or already-finished run id is an error), so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (stop) and resource (pending steps of a run) plus the secondary effect (refund the unused reserved budget). This distinguishes it cleanly from sibling lifecycle tools like alterlab_run_create, alterlab_run_approve, alterlab_run_result and alterlab_run_stream, which cannot be mistaken for it.

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 rather than stated: an agent can infer it is the tool for halting a run that is no longer wanted. There is no explicit when-to-use vs. alternative guidance (e.g. when to cancel versus simply ignoring the result or letting a run finish), and no stated prerequisites such as required ownership or state of the run.

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

All mcp-server toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources