Skip to main content
Glama
Sign In
Markdown3D MCP Server

Markdown3D MCP Server

by MushroomFleet
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

validate_nm3

Validate NM3 XML files to ensure they meet the required specification, preventing processing errors in 3D visualizations.

Instructions

Validate NM3 XML for compliance with spec

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": {
      "xml": "<xml>"
    },
    "name": "validate_nm3"
  }
}

Input Schema

NameRequiredDescriptionDefault
xmlYesNM3 XML to validate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must cover behavioral traits. It indicates 'Validate' (read-only), but does not disclose what happens on failure (e.g., error thrown, return false) or side effects. Lacks depth.

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?

Single sentence with no wasted words. Could benefit from slight expansion, but not overly verbose.

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?

Simple tool with one parameter and no output schema. Description is minimally complete but lacks details on return value (boolean, errors) and the specific spec. Acceptable for a straightforward validation tool.

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

Parameters3/5

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

Schema coverage is 100% with description 'NM3 XML to validate'. Description adds no further meaning beyond schema, so baseline 3 is appropriate. No format, encoding, or size constraints mentioned.

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 clearly states the verb 'Validate' and the resource 'NM3 XML', and mentions compliance with a spec. It distinguishes from sibling tools like transform_to_nm3. However, 'spec' is vague without specifying which standard.

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?

No guidance on when to use this tool versus alternatives (e.g., after transformation, before further processing). No exclusions or prerequisites mentioned.

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