Skip to main content
Glama
Sign In
errorbar

errorbar

by omnia-v
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

stop grpo run

stop_grpo_run

Stop an active GRPO run immediately to halt unexpected spending and release its wallet hold. Use when results or costs diverge from expectations.

Instructions

Stop an ACTIVE online-RL (GRPO) run and release its wallet hold immediately — use it to cut a run short when spend or results aren't what you expected. POST /v1/grpo/runs/{id}/stop (API-key scope: platform:write). Returns: 200 { ok: true }. The run flips to STOPPED; the reward server refuses further scoring and the orchestrator exits on its next sweep. Notes: Idempotency: a run that is not ACTIVE (already stopped/completed) or not in the workspace returns 404 'Run not found or not active'. Money: the commitment hold is released right away; already-metered spend stays billed. Feature-flag gated (fineTuning flag off → 404). OWNER/ADMIN key required (403). No body is read.

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": {
      "id": "<id>"
    },
    "name": "stop_grpo_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe GRPO run id. Must be ACTIVE and belong to the workspace.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.5/5.0
Behavior5/5

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

The description discloses far more than annotations provide: the exact POST endpoint, API scope, 200 response, transition to STOPPED, refusal of further scoring, orchestrator exit, immediate hold release, already-metered spend staying billed, feature-flag gating, auth requirements, 404 behavior, and that no body is read. This is comprehensive behavioral disclosure with no contradiction to annotations.

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?

The description is dense but every sentence earns its place: main purpose is front-loaded, followed by endpoint, response, behavioral side effects, error cases, and auth. No filler or redundancy; the structure makes the information easy to scan.

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

Completeness5/5

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

For a one-parameter tool with no output schema, the description is complete. It covers the return value ('200 { ok: true }'), side effects, error states, auth, feature-flag gating, billing implications, and idempotency behavior. An agent has everything needed to call it correctly.

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 required 'id' parameter is already documented in the schema as 'Must be ACTIVE and belong to the workspace.' The description repeats ACTIVE/workspace context but adds no new parameter-level semantics beyond what the schema already provides, so the baseline 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?

The description uses a specific verb and resource: 'Stop an ACTIVE online-RL (GRPO) run and release its wallet hold immediately.' It clearly identifies this as the stop operation for GRPO runs, distinguishing it from sibling tools like start_grpo_run, get_grpo_run, and list_grpo_runs.

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?

The description gives an explicit when-to-use statement: 'use it to cut a run short when spend or results aren't what you expected.' It also documents key conditions such as 404 for non-ACTIVE runs and OWNER/ADMIN key requirements. However, it does not explicitly name alternative tools or state when not to use it.

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

Deploy Server

Other Tools