Skip to main content
Glama

ai_modeling_job_reconcile

Link an outcome-unknown job or missing export/model batch receipts to exact original Studio IDs after manual reconciliation, using read-only upstream verification with no new generation.

Instructions

Link an outcome_unknown job or missing export/model batch receipts to exact original Studio IDs after manual reconciliation. Read-only upstream verification; no new generation.

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": {
      "job_id": "<job_id>",
      "remote_ids": "<remote_ids>"
    },
    "name": "ai_modeling_job_reconcile"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
remote_idsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true, destructiveHint=false and readOnlyHint=false. The description adds real context beyond that: upstream verification is read-only and "no new generation" occurs, so the agent knows no assets/models will be created. However it does not say what local state is written, whether linking is idempotent, or what happens on a reconciliation mismatch — and the "Read-only" wording sits in mild tension with readOnlyHint=false unless read as scoped to the upstream check only.

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 short sentences, purpose front-loaded, no filler. The trade-off is that the terseness comes at the cost of parameter and behavior detail rather than being wasteful.

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 nested-object mutation with no output schema and zero schema description coverage, the description is too thin — it omits the meaning of remote_ids, the required pairing of job_id with those records, and any indication of the response. It covers intent but not enough to call the tool correctly without reading the raw schema.

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% and the parameters are not flat: remote_ids nests batch[] and models[] arrays (each with project_id/operator_id/index) plus task_id, asset_id, project_id and operator_id. The description says nothing about this structure, the 1–10 item limits, or how batch/model entries map to job output indices, leaving the agent to reverse-engineer the schema alone.

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?

Names a specific verb ("Link") and a specific resource pair (outcome_unknown job / missing export/model batch receipts → original Studio IDs), which differentiates it from the sibling read tools like ai_modeling_job_get or ai_modeling_canvas_batches. The phrasing is dense with domain jargon ("receipts", "outcome_unknown"), but the operation is identifiable.

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 trigger condition is implied: use it when a job's outcome is unknown or batch/model receipts are missing, and only "after manual reconciliation." That precondition is useful, but there is no explicit statement of when NOT to use it or which sibling to use instead (e.g., ai_modeling_job_get for a normal, already-linked job lookup).

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

Deploy Server

Other Tools