Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

native_job_status

Read-onlyIdempotent

Tracks an existing native operation and resumes it by operation ID after a timeout, preventing duplicate writes.

Instructions

Resume the same native operation; never create a second write after a timeout.

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": {
      "operation_id": "<operation_id>"
    },
    "name": "native_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
operation_idYes
wait_secondsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

C2/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is known. The description adds only a retry-safety norm ('never create a second write after a timeout') and discloses nothing about polling behavior, terminal states, or what wait_seconds blocks on. The wording 'Resume the same native operation' also creates mild tension with the read-only hint, since 'resume' reads like a mutation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, so there is no padding. However, the single clause it spends on purpose is vague enough to mislead, meaning the brevity comes at the cost of clarity rather than being earned.

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?

An output schema exists, so return values needn't be spelled out, but with 0% schema coverage the description should carry the parameter meaning and the basic polling contract, and it carries neither. For a two-parameter resume-safe status tool, this leaves the agent guessing at how to invoke it correctly.

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

Parameters1/5

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

Schema description coverage is 0% and the description says nothing about either parameter. It never explains what operation_id identifies or that wait_seconds is a blocking poll duration (default 0), so the agent must infer both from bare titles.

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

Purpose2/5

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

"Resume the same native operation" does not describe a status/polling tool, despite the name native_job_status. The description never states the specific verb+resource (query job status by operation_id), and it is easily confused with a resume/retry action or with native_job_cancel.

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?

It implies a single scenario (after a timeout, re-check rather than re-issue the write), which is useful, but gives no general when-to-use guidance and never distinguishes this from native_job_cancel or asset_job_status. Nothing tells the agent what to do on a non-terminal status or how wait_seconds changes the call.

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