Skip to main content
Glama

Run model fit

run_model_fit
Destructive

Run a released model parameter fit 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_fit"
  }
}

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?

Annotations already flag destructive=true, readOnly=false and idempotent=false; the description adds real value beyond that by disclosing internal validation, asynchronous single-job queuing, authorization and compute-entitlement requirements, and a retry/UUID discipline. It still leaves the destructive dimension vague — it never says credits are consumed or that the operation is unrecoverable — which is the key behavioral fact for a costly mutation.

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 what the tool does and followed by prerequisites and follow-up actions; there is no filler. The only cost is the ambiguous 'Retain the UUID' phrasing, which sacrifices precision for brevity.

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 not be described, and the description does cover validation, queuing, auth, and the retry path. For a destructive, credit-consuming, nested-parameter mutation it is still thin on cost/irreversibility and on the non-obvious parameters, leaving gaps an agent must resolve elsewhere.

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 only 29% across 7 parameters, so the description must carry more weight than it does. It gestures at parameters and destination_project_id, but leaves inputs, limits (including credit_cost and GPU caps), agent_run_id and capability_version unexplained, and 'Retain the UUID' is ambiguous between the idempotency_key and the job identifier returned by the call.

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 parameter fit') scoped by exact parameters and a destination project, which separates it from run_model_scan and run_model_simulation by the 'fit' resource. It stops short of explicitly naming those siblings as alternatives, so differentiation is implied rather than stated.

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?

Usage is only implied: 'Run a released model parameter fit' plus 'inspect request_status after uncertainty' points an agent to the request_status sibling for follow-up. There is no guidance on when to choose a fit over scan/simulation/run_capability, nor on prerequisites such as which entitlements must be held before calling.

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