Skip to main content
Glama
LCM2M

lcm2m-caddis-mcp

by LCM2M

Org unit utilization over time

caddis_get_org_unit_utilization
Read-onlyIdempotent

Retrieve utilization metrics (running/down seconds) for each piece of equipment in an org unit, grouped by time intervals.

Instructions

Utilization metrics aggregated across every piece of equipment under an org unit. Buckets the running/down seconds into intervals (default '1d') over the requested window in the given timezone (default 'UTC'). Returns one entry per bucket.

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
tzNoIANA timezone, e.g. 'America/Denver' (default 'UTC')
endNoISO 8601 window end (defaults to now)
startYesISO 8601 window start (required)
intervalNoBucket interval, e.g. '1h', '1d', '1w' (default '1d')
orgUnitIdYesNumeric identifier (accepts either string or number form)
Behavior4/5

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

Annotations already indicate read-only, idempotent, and open-world behavior. The description adds details on timezone handling, interval bucketing, and response format (TOON encoding), providing additional behavioral context beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads the purpose but includes a lengthy explanation of the TOON encoding format. While necessary due to non-standard output, it reduces conciseness.

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 no output schema, the description thoroughly explains the result format and aggregation logic. It covers defaults but does not mention pagination or query limits, leaving minor gaps.

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?

Input schema descriptions cover 100% of parameters. The description mentions default values for 'interval' and 'tz' but does not add further semantic meaning beyond what schema already 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?

The description clearly states it aggregates utilization metrics for all equipment under an org unit, with bucketing into intervals. This differentiates it from sibling tool 'caddis_get_equipment_utilization' which is per-equipment.

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 does not explicitly state when to use this tool versus alternatives like 'caddis_get_equipment_utilization'. Usage context is implied by the name and description but lacks direct guidance.

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