Skip to main content
Glama

ai_modeling_motion_task

Read-only

Inspect a single AI motion generation task by task ID to check its status, progress, and results within the ai-modeling workflow.

Instructions

Inspect one AI motion generation task.

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": {
      "task_id": "<task_id>"
    },
    "name": "ai_modeling_motion_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: it does not say whether inspection returns status, progress, or error state, nor that a task may be pending/failed, which matters for an async generation task.

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?

A single six-word sentence with zero padding and the resource front-loaded, which is structurally clean. However, the brevity crosses into under-specification rather than economy, so it earns only partial credit here.

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?

The tool has one required parameter, no output schema, and read-only annotations, so the description is the only place an agent can learn what inspection actually yields. It fails to cover return content or task-state semantics, leaving the agent guessing about the response shape.

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 coverage is 0%, so the description must carry the burden for the single required parameter. The word "one" weakly implies task_id selects a single task, but there is no mention of the expected identifier format (the schema's pattern allows colons, dots, underscores) or where such an id comes from.

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?

"Inspect one AI motion generation task" gives a verb and a resource and signals single-item scope, so the basic purpose is legible. But it never distinguishes itself from near-identical siblings such as ai_modeling_task_get or ai_modeling_motion_get, leaving an agent unsure which inspector to pick.

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 when-to-use guidance, no prerequisite conditions (e.g. that the task must already exist), and no named alternative. The agent must infer from the name alone when this tool beats the sibling getters.

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