Skip to main content
Glama
architectural_modeling_workflow

architectural_modeling_workflow

by Lsc1123

asset_job_status

Read-onlyIdempotent

Check durable worker status, Blender exit code, and saved/reimport verification for a specified operation to confirm asset processing completed correctly.

Instructions

Return durable worker status, Blender exit code and saved/reimport verification.

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": "asset_job_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
operation_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that results are durable and include exit code plus saved/reimport verification, which signals meaningful internal behavior beyond the annotations, though it says nothing about polling, retention, or failure states.

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?

One compact sentence with no filler, and the key output content is front-loaded. The phrase "durable worker status" is somewhat jargon-heavy but stays efficient overall.

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?

Because an output schema exists, the description need not enumerate return fields, and it correctly focuses on distinguishing content. What is missing for an agent to actually invoke it is the provenance and lifetime of operation_id, which neither schema nor description supplies.

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% for the single required operation_id parameter, and the description never mentions it or explains where the id originates (presumably from asset_build). With zero schema help, the description should have specified this but does not.

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?

States a specific verb ("Return") and specific resources (durable worker status, Blender exit code, saved/reimport verification), so an agent knows this is a status-read tool for an asset job. It does not, however, distinguish itself from the sibling native_job_status, leaving ambiguity about which job family each one covers.

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?

There is no statement of when to call this tool, when not to, or which alternative to use for native versus asset jobs. The agent must infer that this pairs with asset_build and must not use it for native jobs, purely from the name.

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