i3X-MCP-Server

Describe ObjectType

describe_type

Retrieve the JSON Schema and per-field units for a given ObjectType element ID, enabling understanding of manufacturing data structure and units.

Instructions

Returns the JSON Schema and per-field units for an ObjectType.

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": {
      "typeElementId": "<typeElementId>"
    },
    "name": "describe_type"
  }
}

Input Schema

Name	Required	Description	Default
`typeElementId`	Yes	ObjectType elementId.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jun 25, 2026

TDQS

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden. It only states what is returned (JSON Schema and units) but gives no information about side effects, permissions, or read-only nature. For a read-only metadata tool, basic details are present but insufficient.

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 a single sentence that front-loads the key action and result. No extraneous words, making it highly efficient for an AI agent to parse.

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

Completeness4/5

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

Given the simplicity (1 param, no output schema, no annotations), the description covers the essential information. Minor gaps exist (e.g., what 'per-field units' means, or any restrictions), but it is largely complete for a straightforward reflection tool.

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

Parameters4/5

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

The parameter typeElementId is described in the schema as 'ObjectType elementId'. The tool description adds context by linking this parameter to the ObjectType being described, reinforcing its purpose. Since schema coverage is 100%, the description adds value beyond the schema.

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 that the tool returns the JSON Schema and per-field units for an ObjectType. The verb 'Returns' and specific resource 'ObjectType' make the purpose unambiguous, distinguishing it from sibling tools like get_object or search_objects.

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

Usage Guidelines3/5

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

The description implies usage (when you need schema and units for a type) but provides no explicit guidance on when not to use it or alternatives among siblings. This is adequate for a simple tool with a single parameter.

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

Deploy Server