Skip to main content
Glama
LCM2M

lcm2m-caddis-mcp

by LCM2M

Org unit schedule

caddis_get_org_unit_schedule
Read-onlyIdempotent

Retrieves current schedule for an organizational unit, showing inheritance source and resolved timezone in TOON-encoded format.

Instructions

Current schedule for an organizational unit, with inheritance source and resolved timezone.

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
orgUnitIdYesNumeric identifier (accepts either string or number form)
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld hints. The description adds minor value by confirming the response contains inheritance and timezone info, but does not elaborate on rate limits, side effects, or authorization.

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

Conciseness2/5

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

The first sentence is concise, but the lengthy TOON-format tutorial is excessive and dilutes the core purpose. It should be a separate guide or referenced.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description must detail the return structure. While it explains the TOON format, it omits what fields the schedule contains (e.g., events, time slots). The example uses 'equipment' which is misleading for an org unit schedule.

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 fully describes the single parameter (orgUnitId). The description does not add further meaning, achieving baseline for 100% coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it returns a schedule with inheritance source and timezone, but fails to explicitly differentiate from sibling tools like caddis_get_org_unit_utilization. The purpose is clear enough but not sharp.

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 vs alternatives (e.g., other schedule tools). The tool's context is implied by name only.

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