Skip to main content
Glama
niknarra

x3d-mcp

by niknarra

x3d_animate

Animate any X3D node field by generating a complete animation chain (TimeSensor, interpolator, ROUTEs) and inserting it into the scene.

Instructions

Generate a complete X3D animation chain and insert it into a scene.

Creates a TimeSensor, the appropriate Interpolator (auto-selected based
on the target field's type), and ROUTE statements to wire them together.
Inserts all nodes into the scene and returns the modified X3D document.

Args:
    x3d_source: Complete X3D XML document string or file path.
    target_def: DEF name of the node to animate (e.g., "MyTransform").
    field_name: Field to animate. Examples:
                - "rotation" → OrientationInterpolator
                - "translation" → PositionInterpolator
                - "diffuseColor" → ColorInterpolator
                - "transparency" → ScalarInterpolator
    from_value: Starting value as a space-separated string (e.g., "0 1 0 0").
    to_value: Ending value as a space-separated string (e.g., "0 1 0 6.283").
    duration: Animation cycle duration in seconds. Default 5.0.
    loop: Whether the animation loops continuously. Default True.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
loopNo
durationNo
to_valueYes
field_nameYes
from_valueYes
target_defYes
x3d_sourceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries full responsibility for behavioral transparency. It reveals key behaviors: creates a TimeSensor, auto-selects the appropriate Interpolator based on field type, creates ROUTE statements, inserts all nodes, and returns the modified X3D document. It also documents parameter defaults (duration, loop), giving an agent a clear understanding of side effects.

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

Conciseness5/5

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

The description is well-structured: a one-sentence purpose summary, a brief behavioral explanation, and a precise Args list. Every sentence contributes value, with no repetition or filler. The front-loaded summary and organized details make it easy to scan.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 7-parameter tool with an output schema, the description covers purpose, mechanism, parameter meanings, and return behavior ('returns the modified X3D document'). It is self-contained and sufficient for correct invocation, even without an explicit description of return values (since an output schema exists).

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

Parameters5/5

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

Schema description coverage is 0%, but the description's Args section thoroughly explains every parameter with X3D-specific examples (e.g., 'rotation' → OrientationInterpolator, 'from_value' as a space-separated string). This fully compensates for the missing schema descriptions, adding meaning beyond the property names.

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

Purpose5/5

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

The description opens with a clear verb+resource: 'Generate a complete X3D animation chain and insert it into a scene.' It distinguishes itself from sibling tools like x3d_generate_node and x3d_route by specifying the full chain (TimeSensor, Interpolator, ROUTEs) and the auto-selection behavior.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context on when to use the tool: to animate a node's field. It explains the automated interpolator selection, implying this is the high-level animation tool rather than manual route creation. However, it does not explicitly name alternatives or provide 'when not to use' guidance, so it stops short of a 5.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/niknarra/x3d-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server