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

i3X-MCP-Server

by cesmii
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

List root objects

list_root_objects

Retrieve top-level objects in the i3X hierarchy to start exploring equipment or plant structure. Optionally include descriptions and relationships.

Instructions

Returns top-level objects in the i3X hierarchy (no parent). Good entry point for unfamiliar plants.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_root_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeMetadataNoInclude descriptions and relationships (default false).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses the scope (top-level, no parent) but lacks details on auth, rate limits, or pagination. Adequate for a simple read operation.

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?

Two concise sentences front-load the core purpose and use case. No redundant text.

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 list tool with one optional param and no output schema, the description covers essential behavior. Could mention return format but not critical given context.

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?

Single parameter 'includeMetadata' fully described in schema (100% coverage). Tool description adds no extra meaning beyond schema, meeting baseline but not compensating further.

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?

Clearly states it returns top-level objects with no parent, and positions it as an entry point for exploration. Distinguishes from sibling tools like search_objects or get_object.

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?

Indicates use case as a good entry point for unfamiliar plants, implying initial exploration. Lacks explicit when-not-to-use or alternatives, but context is clear given sibling names.

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