Skip to main content
Glama
niknarra

x3d-mcp

by niknarra

x3d_route

Validate and insert a ROUTE into an X3D scene by checking DEF names, field names, access types, and matching field types. Connect event outputs to inputs correctly.

Instructions

Validate and insert a ROUTE statement into an X3D scene.

ROUTEs connect event outputs to event inputs in X3D's event system.
This tool validates that both DEF names exist, field names are valid,
access types are compatible, and field types match before inserting.

Args:
    x3d_source: Complete X3D XML document string or file path.
    from_node: DEF name of the source node.
    from_field: Output field on the source (must be outputOnly or inputOutput).
    to_node: DEF name of the destination node.
    to_field: Input field on the destination (must be inputOnly or inputOutput).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_nodeYes
to_fieldYes
from_nodeYes
from_fieldYes
x3d_sourceYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Since no annotations are provided, the description carries the full burden. It discloses the validation steps (checking DEF existence, field validity, access type compatibility, and type matching) and specifies field access constraints. However, it does not state whether the input source is mutated or a new scene is returned, though the presence of an output schema mitigates this gap.

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 and front-loaded with a clear purpose. It uses a concise overview, contextual explanation, and a clear Args list without redundancy. Every sentence contributes value.

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 tool with five required parameters and no annotations, the description covers the tool's purpose, validation behavior, and parameter constraints thoroughly. It also mentions the input format (XML or file path). The presence of an output schema means return values need not be described, so the description is contextually complete.

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?

The description adds significant meaning beyond the raw schema by explaining each parameter: x3d_source is a full XML string or file path, from_node is a DEF name, from_field must be an outputOnly or inputOutput field, etc. This is essential given the schema provides only names and types.

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 clearly states the tool's specific action: "Validate and insert a ROUTE statement into an X3D scene." It names a specific resource (X3D scene) and a distinct task (ROUTE insertion) that separates it from sibling tools like x3d_add_node or x3d_animate.

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 explains the purpose of ROUTEs and when this tool is relevant (connecting event outputs to inputs). It does not explicitly mention alternative tools or when not to use it, but the context is clear enough for an agent to select it for ROUTE creation.

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