Skip to main content
Glama

start_run

Idempotent

Reserve TRIAL credits and queue the quoted execution. Enforces max_price and available balance. Reuse the same quote_id, max_price and idempotency_key after ambiguous failures. Still obey the human's aggregate budget.

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": {
      "quote_id": "<quote_id>",
      "max_price": "<max_price>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "start_run"
  }
}

Input Schema

NameRequiredDescriptionDefault
quote_idYes
max_priceYes
idempotency_keyYesStable purchase idempotency key

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 readOnlyHint=false, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: it spends TRIAL credits, enforces max_price and available balance server-side, and constrains spending against a human's aggregate budget — none of which appears in the annotations. It is consistent with idempotentHint=true. It does not describe failure modes such as insufficient balance or a quote that has expired.

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?

Four short sentences, front-loaded with the action and the spend constraint, then the enforcement rule, then the retry rule, then the budget caveat. Every sentence carries information. 'Still obey the human's aggregate budget' is slightly clipped and would be clearer as a statement that spending must stay within a caller-visible budget.

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 three-required-parameter credit-spending mutation with no output schema, the description covers the important behavioral risks: what is consumed, what caps apply, and how to retry safely. It never says what a successful call returns (presumably a run identifier the agent needs for the claim_run/accept_run siblings), nor what errors to expect. That omission matters more here because no output schema exists to fill the gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%: quote_id and max_price are undocumented in the schema. The description compensates by establishing that max_price is an enforced ceiling, that quote_id identifies a specific quoted execution, and that idempotency_key is what makes retries safe. The remaining gap is that max_price units (credits? micro-credits?) and the quote_id provenance are never stated.

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 a specific verb pair and resource: 'Reserve TRIAL credits and queue the quoted execution.' That distinguishes it from state-transition siblings such as claim_run, accept_run, or cancel_run, which operate on an existing run rather than creating one from a quote. It does not name an alternative explicitly, so it stops short of 5.

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?

There is real guidance for one scenario: reuse the same quote_id, max_price, and idempotency_key after ambiguous failures, which tells the agent to retry rather than re-quote. However, there is no guidance on when to call this versus quote_capability (must a quote exist first?) or versus list_runs/get_run to check whether a run already started. Usage is implied by the required quote_id 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