Skip to main content
Glama

ai_modeling_job_get

Read-only

Refresh an existing AI modeling job by its original remote ID without resubmitting generation; optionally wait up to 30 seconds for updated status.

Instructions

Refresh a job using its original remote ID. Never resubmits generation. wait_seconds is bounded to 30.

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>"
    },
    "name": "ai_modeling_job_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
job_idYes
wait_secondsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful guarantee beyond that: "Never resubmits generation," which reassures the agent this is a safe poll rather than a re-run. It stops short of explaining what a refresh actually does server-side or what the caller receives.

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?

Three short, front-loaded sentences with no filler. The only waste is the trailing sentence restating a constraint the schema already encodes as maximum: 30.

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 two-parameter, read-only tool with no output schema, the description covers the essentials but leaves real gaps: what a refreshed job object contains, whether the call blocks for wait_seconds, and how it relates to the reconcile sibling. Adequate rather than complete.

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

Parameters3/5

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

Schema description coverage is 0%, so the description must compensate, and it partially does: "original remote ID" clarifies that job_id is the remote-side identifier rather than a local handle. The wait_seconds note merely restates the schema's maximum of 30, adding no new meaning.

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?

"Refresh a job using its original remote ID" names a verb and a resource, but the verb is ambiguous relative to the tool name ai_modeling_job_get and to siblings like ai_modeling_job_reconcile. An agent cannot tell from the description alone whether this fetches status, re-polls the backend, or re-syncs local state.

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-to-use guidance is given. The description never mentions polling, retries, or how this differs from ai_modeling_job_reconcile, which an agent would likely confuse it with given the near-identical purpose implied by the name.

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