Skip to main content
Glama

ai_modeling_animation_remove

Remove one applied animation from a project by providing the project ID and the associated model and retarget operator IDs.

Instructions

Remove one applied animation from a project.

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": {
      "project_id": "<project_id>",
      "model_operator_id": "<model_operator_id>",
      "retarget_operator_id": "<retarget_operator_id>"
    },
    "name": "ai_modeling_animation_remove"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
model_operator_idYes
retarget_operator_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.6/5.0
Behavior2/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the agent knows this mutates state without being flagged destructive. The description adds nothing beyond that: it does not say whether removal is reversible, whether re-applying is possible, whether unknown references error out, or whether other applied animations are untouched. The word 'Remove' is consistent with destructiveHint=false only if interpreted as reverting an applied configuration, which the description never clarifies.

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 a single well-formed sentence with zero filler, which is appropriately front-loaded. However, the brevity reflects under-specification rather than real conciseness, so it is only marginally adequate.

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 state-changing tool with three undocumented identifier parameters, no output schema, and no parameter descriptions anywhere, the definition is too thin. An agent cannot confidently construct the operator identifiers or predict the result of a failed removal from this description alone.

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%, so the schema only supplies names, types, and regex patterns. The description hints at a project and at a single animation reference, but says nothing about what model_operator_id and retarget_operator_id represent or how they jointly identify the animation to remove, leaving two of three required parameters opaque.

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?

The description names a specific verb ('Remove'), a specific resource ('one applied animation'), and scope ('from a project'), so there is no ambiguity about the operation. It does not distinguish itself from related animation operations (e.g., applying or listing animations), but the core purpose is unmistakable.

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?

The description gives no guidance about when to use this tool, when not to, or what alternative to choose. It does not state prerequisites, such as the animation having already been applied, or what happens if the animation reference is unknown.

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