Skip to main content
Glama
LCM2M

lcm2m-caddis-mcp

by LCM2M

Run multiple caddis_* tools in parallel

caddis_batch
Read-onlyIdempotent

Execute up to 20 caddis tool requests in parallel with a single call. Each request is dispatched individually, preserving retry and login behavior, and returns a prefixed text block per result.

Instructions

Run multiple caddis_* tools in a single call, fanning out in parallel. Each request in requests is dispatched to the same handler the tool would run individually, so 429 retry/jitter and login-dedup behavior is preserved. Up to 20 requests per call; concurrency is capped at 1 in-flight. Response contains one text block per request, in input order, each prefixed with #<index> <tool> <ok|error>. One failed request does not sink the batch.

Available tools: caddis_get_company, caddis_get_device, caddis_get_equipment, caddis_get_equipment_cycles, caddis_get_equipment_excessive_downtime, caddis_get_equipment_schedule, caddis_get_equipment_shift_history, caddis_get_equipment_statuslogs, caddis_get_equipment_telemetry, caddis_get_equipment_utilization, caddis_get_org_unit, caddis_get_org_unit_schedule, caddis_get_org_unit_utilization, caddis_get_run, caddis_get_run_cycles, caddis_get_tag, caddis_get_tag_group, caddis_get_tree, caddis_list_alarms, caddis_list_categories, caddis_list_devices, caddis_list_equipment, caddis_list_equipment_excessive_downtimes, caddis_list_manufacturers, caddis_list_models, caddis_list_org_unit_excessive_downtimes, caddis_list_runs, caddis_list_status_reasons, caddis_list_tag_groups, caddis_list_tags

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
requestsYesUp to 20 tool invocations to run in parallel. Each is dispatched to the same handler the tool would run individually, so existing 429 retry, jitter, and login-dedup behavior applies per request.
Behavior5/5

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

Beyond annotations (readOnlyHint, idempotentHint, openWorldHint), the description adds parallel dispatch, retry/dedup preservation, failure isolation ('One failed request does not sink the batch'), and response format (prefix per request).

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 relatively concise, front-loaded with core purpose, and lists available tools as an unordered set. While the tool list is lengthy, it is necessary for clarity.

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?

For a batch tool with no output schema, the description covers input, behavior (parallelism, limits, error handling), and response format (prefixed text blocks). No obvious 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?

The input schema has 100% coverage on the 'requests' parameter; the description adds behavioral context but does not add semantic meaning beyond the schema's 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 'Run multiple caddis_* tools in a single call, fanning out in parallel' with a specific verb and resource, and lists all available tools, distinguishing it from individual sibling tools.

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 mentions limits (up to 20 requests, concurrency capped at 1) and preserved retry behavior but lacks explicit when-to-use or when-not-to-use guidance versus individual calls.

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