Skip to main content
Glama
Sign In
i3X-MCP-Server

i3X-MCP-Server

by cesmii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get object details

get_object

Retrieve detailed information about specified objects, including their type, parent, composition, and declared relationships.

Instructions

Detailed info for one or more objects: type, parent, composition flag, declared relationships.

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": {
      "elementIds": "<elementIds>"
    },
    "name": "get_object"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementIdsYesElement IDs to look up.
includeMetadataNoInclude descriptions and full relationship graph (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Describes returned fields but does not explicitly state it is a read-only operation or mention error handling, performance, or effects on the system. With no annotations, more disclosure is needed.

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?

Single sentence, front-loaded with key purpose and attributes. No wasted words.

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?

For a simple lookup tool, description adequately explains return content (type, parent, composition flag, declared relationships). Lacks mention of handling multiple objects or potential limitations like pagination, but still reasonably complete.

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% (both parameters have descriptions). Description adds no additional semantic value beyond what the schema provides.

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?

Description clearly states the tool retrieves detailed info for objects including type, parent, composition flag, and relationships. It distinguishes from siblings like 'find_related' and 'list_root_objects' by specifying exact attributes returned.

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 over alternatives such as 'find_related', 'get_history', or 'read_current_value'. No context for prerequisites or exclusion criteria.

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