Skip to main content
Glama

run_submit

DestructiveIdempotent

Persists a simulation run submission request and returns immediately, ensuring repeated calls return the same run and reconciling unknown dispatches first.

Instructions

Persist submission intent and return immediately. Repeated calls return the same run; unknown dispatch reconciles 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>",
      "revision": "<revision>",
      "op_id": "<op_id>"
    },
    "name": "run_submit"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
tokenNo
run_idYes
revisionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true; the description usefully confirms the idempotency semantics ("repeated calls return the same run") and adds that it is non-blocking. It does not explain what is destroyed, what permission or token requirements exist, or what "unknown dispatch reconciles first" actually means. Added context is real but partial, so a 3 fits.

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?

Two tight sentences with the key behavior front-loaded and no filler. The second clause ("unknown dispatch reconciles first") is compressed to the point of being cryptic, which costs a point.

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, open-world mutation with a token parameter and 0% schema coverage, the description omits what gets created or destroyed, what reconciliation implies, and what the token authorizes. The output schema existing relieves only the return-value burden.

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

Parameters2/5

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

Schema description coverage is 0% across four parameters (run_id, revision, op_id, token), so the description carries the full burden. It never names or explains any of them; the idempotency comment only indirectly gestures at op_id semantics, leaving revision and token entirely opaque.

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

Purpose3/5

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

"Persist submission intent and return immediately" gives a verb (persist) and an intent (submit a run), but "submission intent" is abstract enough that the agent must infer that this actually dispatches/submits a run. Nothing distinguishes it from siblings such as run_prepare, run_action, analysis_submit, or batch_submit.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not guidance is given, and no alternative is named. The agent cannot tell from this text whether to call run_submit versus run_prepare or run_action for a given situation.

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