Skip to main content
Glama
LCM2M

lcm2m-caddis-mcp

by LCM2M

Get the org unit / equipment tree

caddis_get_tree
Read-onlyIdempotent

Fetch the full company tree or a subtree of organizational units, equipment, and devices to understand the hierarchy and ownership.

Instructions

Structural overview of the org-unit hierarchy with the equipment and devices under it. Without orgUnitId, returns the full company tree from the root; with orgUnitId, returns the subtree rooted there. The body is a TOON document with three named tabular sections — org_units[...]{...}:, equipment[...]{...}:, and devices[...]{...}: — each followed by its indented rows. Hierarchy is encoded in the path columns rather than nesting: each org_units row carries parent_id and parent_path (dot-delimited ancestor ids, e.g. "root.1.2"), each equipment row carries parent_org_unit_id and parent_org_unit_path, and each devices row carries equipment_id. Reconstruct the tree by joining on these. Schedules, device input_setup, hardware_info, and other nested config blobs are NOT included here — fetch them via caddis_get_org_unit_schedule, caddis_get_equipment_schedule, caddis_get_equipment, or caddis_get_device when needed.

Responses are TOON-encoded (toonformat.dev) — a token-efficient JSON dialect mixing YAML-style indentation with CSV-style tables. Example:

name: Caddis Co timezone: America/Denver equipment[3]{id,name,tags,current_status.status,current_status.reason_id}: 1,Mill A,"["cnc","critical"]",running,null 2,"Press, Big",null,down,3 3,Lathe C,null,null,null

  • Object fields: key: value; nested objects indent their children.

  • Uniform arrays of objects: field[N]{cols}: followed by N indented comma-separated rows in column order.

  • Nested objects inside table rows are recursively flattened to dotted columns (e.g. current_status.status, input_setup.cycle.logic); a null parent yields null across all its dotted columns (see row 3 above).

  • Primitive arrays at object level: field[N]: a,b,c inline.

  • Arrays inside table cells are JSON-stringified into a single cell value (JSON.parse() to recover); empty arrays render as null (see rows 1–3 tags column).

  • Strings with commas/colons/quotes/leading whitespace are double-quoted (escapes: \\, \"); other strings, numbers, booleans, and null are bare.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
orgUnitIdNoRoot for the subtree; omit for the full company tree
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent. The description adds detailed behavioral context: response is a TOON document, hierarchy is encoded in path columns, and how to reconstruct the tree. No contradiction with annotations.

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?

The description is long but well-structured: main purpose first, then parameter behavior, then TOON format explanation with examples. Every sentence is informative; however, the TOON format explanation could be referenced as an external link.

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?

Given no output schema and the complexity of the TOON format, the description is exceptionally complete. It covers the response structure, how to interpret hierarchy, and what data is absent. An example clarifies formatting rules.

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?

Schema coverage is 100% and the parameter is simple. The description explains the semantic effect of providing or omitting orgUnitId (full tree vs subtree). This adds context beyond the schema property description.

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 'Structural overview of the org-unit hierarchy with the equipment and devices under it,' specifying the verb 'get' and the resource 'tree.' It further distinguishes from siblings by listing data not included (schedules, config blobs) and providing alternative tool names.

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

Usage Guidelines5/5

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

It explicitly states when to use the tool (structural overview) and the effect of the optional parameter: without orgUnitId returns full tree, with orgUnitId returns subtree. It also lists exactly what is not included and names alternative tools for those needs.

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/LCM2M/lcm2m-caddis-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server