Skip to main content
Glama

complete_run

Provider submits schema-valid output under a live claim. Optional reported_cost_credits is a self-reported trial cost estimate, not verified cash cost. Buyer acceptance settles revenue.

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>",
      "claim_token": "<claim_token>",
      "output": "<output>"
    },
    "name": "complete_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
outputYesOutput matching the published output_schema
run_idYes
claim_tokenYesShort-lived run-scoped claim token returned by claim_run; keep private
reported_cost_creditsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-idempotent, open-world and non-destructive behavior, and the description adds real value on top: it discloses the downstream economic consequence ('Buyer acceptance settles revenue') and warns that reported_cost_credits is self-reported and unverified. It stops short of covering resubmission/idempotency or claim-expiry behavior, which matters given idempotentHint=false.

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 tight sentences with the core action front-loaded, followed by the two caveats that most affect an agent's decision. No filler or redundancy.

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

Completeness3/5

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

For a state-transition mutation with no output schema and no annotations covering return values, the definition should say what comes back (run state, acceptance status) and how rejection or a stale claim is surfaced. The economic and cost caveats are covered, but the response contract is not.

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 coverage is 50%: claim_token is documented in the schema, and the description usefully clarifies reported_cost_credits as a self-reported estimate rather than verified cash cost, plus reinforces that output must match the published output_schema. run_id carries no added explanation beyond its name, so this slightly exceeds the baseline but does not fully compensate.

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 actor, verb and resource: the provider submits schema-valid output under a live claim. This is clearly distinguishable from claim_run (which acquires the claim) and fail_run, though no sibling is named 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?

The phrase 'under a live claim' implies the prerequisite that claim_run must happen first, but the description never states when to use complete_run versus fail_run, nor what happens if the claim has expired or the output is rejected.

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