Skip to main content
Glama
AnuwatThisuka

CMMS MCP Server

get_devices

Retrieve IoT devices from manufacturing systems with optional filters for status or type to monitor operational assets.

Instructions

Get IoT devices. Can filter by status or type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by device status
typeNoFilter by device type

Implementation Reference

  • The handler function `handleGetDevices` that processes the tool request.
    private handleGetDevices(args: { status?: string; type?: string }) {
      let devices = [...mockDevices];
    
      if (args.status) {
        devices = devices.filter((d) => d.status === args.status);
      }
      if (args.type) {
        devices = devices.filter((d) => d.type === args.type);
      }
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(devices, null, 2),
          },
        ],
      };
    }
  • src/index.ts:312-325 (registration)
    Registration of the `get_devices` tool, including its input schema and description.
    name: "get_devices",
    description: "Get IoT devices. Can filter by status or type.",
    inputSchema: {
      type: "object",
      properties: {
        status: {
          type: "string",
          enum: ["online", "offline", "error"],
          description: "Filter by device status",
        },
        type: {
          type: "string",
          description: "Filter by device type",
        },
Behavior2/5

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

No annotations provided, so description carries full disclosure burden. While 'Get' implies a read operation, there is no information about pagination, rate limits, return format, or error states. Insufficient for a tool in a complex system with many related endpoints.

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?

Extremely concise with two short sentences. However, given the lack of annotations and presence of many sibling tools, this brevity comes at the cost of necessary context. Structure is front-loaded but undersized for the tool's complexity.

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?

Inadequate for the complexity implied by 11 sibling tools and no annotations or output schema. No explanation of how devices relate to sensors/assets, no pagination details, and no return value description. The description meets only the bare minimum for a standalone tool.

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 the schema already documents both parameters. The description confirms filtering is optional (consistent with 0 required parameters), but adds no syntax details, format examples, or semantic meaning beyond the schema definitions.

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?

States the basic action ('Get') and resource ('IoT devices'), but fails to distinguish from siblings like get_sensors, get_assets, or get_equipment which may overlap conceptually in an IoT system. Lacks specificity on what constitutes a 'device' versus these related resources.

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 this tool versus alternatives like get_sensors or get_assets. The phrase 'Can filter by status or type' describes capability, not selection criteria or prerequisites for use.

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/AnuwatThisuka/cmms-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server