Skip to main content
Glama
LCM2M

lcm2m-caddis-mcp

by LCM2M

Equipment production cycles

caddis_get_equipment_cycles
Read-onlyIdempotent

Retrieve production cycles for equipment within a time window. Returns data in compact TOON format for token-efficient analysis.

Instructions

Production cycles (individual part/unit runs) for a piece of equipment within a time window. Keep windows and limits modest — cycle counts can be very high.

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
endNoISO 8601 window end (defaults to now)
limitNoMax rows to return (backend default 5000). Keep modest to avoid token-blowing large response bodies.
orderNoSort order, 'ASC' or 'DESC' (default DESC)
startYesISO 8601 window start (required)
equipIdYesNumeric identifier (accepts either string or number form)
Behavior5/5

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

Annotations already mark it as read-only and idempotent. The description adds valuable behavioral details: response format (TOON-encoded) with a comprehensive example and rules, plus a warning about large responses. This goes well 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.

Conciseness5/5

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

The description is efficiently structured: first sentence states purpose, then a warning, then a detailed but organized explanation of the TOON format with clear bullet points. Every sentence adds value given the non-standard output format.

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?

The description includes output format and performance guidance, which is critical since no output schema exists. It covers required params and default behavior implicitly through the schema. Minor missing explicit restatement of defaults (limit, order) in the main description, but overall 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%, so all parameters are already described. The description does not add new semantics beyond mentioning 'time window' and the format, but the schema itself is sufficient. Baseline 3 applies.

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 defines the tool's purpose: 'Production cycles (individual part/unit runs) for a piece of equipment within a time window.' It uses a specific verb ('get' implied) and resource ('equipment cycles'), distinguishing it from sibling tools like schedule or utilization.

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?

The description advises to keep windows and limits modest due to high cycle counts, providing important usage context. However, it does not explicitly compare to siblings like caddis_get_run_cycles or state when to use this tool over others, which would elevate it to a 5.

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