Skip to main content
Glama
LCM2M

lcm2m-caddis-mcp

by LCM2M

Get one cycle tag

caddis_get_tag
Read-onlyIdempotent

Fetch a single cycle tag by numeric ID. The response uses TOON encoding for token-efficient JSON representation.

Instructions

Fetch a single cycle tag by ID.

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
tagIdYesNumeric 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 and idempotent behavior. The description adds significant value by explaining the TOON-encoded response format with a detailed example and rules. This helps the agent interpret the output, going beyond what annotations provide.

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 is front-loaded with the purpose, but the extensive TOON format explanation makes it verbose. While informative, it could be more concise by referencing external documentation. Every sentence is earned, but overall length is disproportionate for a simple fetch tool.

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 tool with one parameter, no output schema, and read-only annotations, the description covers the purpose, parameter, and response format comprehensively. It lacks only potential error conditions or null scenarios, which are minor for this use case.

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% with one parameter (tagId) already described in the schema. The description does not add further meaning or usage context for the parameter, so baseline score of 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 title 'Get one cycle tag' and description 'Fetch a single cycle tag by ID' clearly state the tool's action and resource. It distinguishes from siblings like caddis_list_tags (lists all tags) and caddis_get_tag_group (gets a group).

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, nor provide conditions or exclusions. The usage is implied by the naming, but no guidance is given for an AI agent to decide between this and other tag-related tools.

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