Skip to main content
Glama

Run model simulation

run_model_simulation
Destructive

Run a released model simulation with exact parameters and destination. Validates internally, then queues one job. Requires authorization and compute entitlements. Retain the UUID for retries; inspect request_status after uncertainty.

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": {
      "parameters": "<parameters>",
      "destination_project_id": "<destination_project_id>",
      "idempotency_key": "<idempotency_key>"
    },
    "name": "run_model_simulation"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputsNo
limitsNoOptional maximum cost and resources; missing estimates block execution. 1000 cpu_millis = 1 vCPU.
parametersYes
agent_run_idNo
idempotency_keyYesOne UUID retained for this logical mutation and its retries.
capability_versionNo
destination_project_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Beyond the annotations (readOnly=false, destructive=true, openWorld=false), the description discloses internal validation before queuing, a single queued job (async), authorization and entitlement gating, and the retry/inspect-request_status recovery path — genuinely additive. What it omits is what 'destructive' actually costs here (credit consumption / resource spend) and why idempotentHint=false given a retained idempotency key.

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, with no filler. Compression is occasionally at the expense of clarity ('with exact parameters' is terse to the point of ambiguity), but nothing is wasted.

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?

An output schema exists, so return values need no explanation, and the description covers the run/validate/queue lifecycle and retry handling. For a 7-parameter, nested-object, credit-consuming, destructive mutation with 29% schema coverage, the unexplained parameters and the unstated cost/destructiveness are material gaps.

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 coverage is only 29% across 7 parameters including a nested `limits` object, so the description carries substantial explanatory burden — but it only alludes to 'exact parameters' and 'destination' and the UUID. `inputs`, `limits`, `capability_version`, and `agent_run_id` get no meaning from the description, and it does not explain that missing resource estimates block execution.

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 states a specific verb and resource — 'Run a released model simulation' — plus the two things it consumes (exact parameters and a destination), which lets an agent separate it from siblings like run_model_fit or run_model_scan. It never explicitly contrasts itself with those siblings, but the resource noun does most of the disambiguation work.

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 useful implied guidance: the model must be 'released', authorization and compute entitlements are prerequisites, and the UUID must be retained for retries. However, it never states when to choose this over run_model_fit / run_model_scan / run_capability, nor any when-not conditions.

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