Skip to main content
Glama
AnuwatThisuka

CMMS MCP Server

get_equipment

Retrieve equipment status from MES systems to monitor operational states, filter by running, idle, maintenance, or error conditions, and access specific equipment details for maintenance management and asset tracking.

Instructions

Get equipment status from MES system. Can filter by status or get specific equipment.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by equipment status
equipmentIdNoGet specific equipment by ID

Implementation Reference

  • The handler function 'handleGetEquipment' that implements the 'get_equipment' tool logic by filtering mock data.
    private handleGetEquipment(args: { status?: string; equipmentId?: string }) {
      let equipment = [...mockEquipment];
    
      if (args.equipmentId) {
        equipment = equipment.filter((e) => e.id === args.equipmentId);
      } else if (args.status) {
        equipment = equipment.filter((e) => e.status === args.status);
      }
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(equipment, null, 2),
          },
        ],
      };
  • src/index.ts:104-115 (registration)
    The registration of the 'get_equipment' tool in the MCP tool list.
    name: "get_equipment",
    description:
      "Get equipment status from MES system. Can filter by status or get specific equipment.",
    inputSchema: {
      type: "object",
      properties: {
        status: {
          type: "string",
          enum: ["running", "idle", "maintenance", "error"],
          description: "Filter by equipment status",
        },
        equipmentId: {
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It mentions the external MES system dependency but fails to disclose read-only nature, error handling behavior, rate limits, or return structure.

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?

Two efficient sentences with no waste. The first sentence establishes purpose and system context; the second explains capabilities. Every word earns its place.

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

Completeness3/5

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

Adequate for a simple 2-parameter getter with complete schema documentation, but lacks differentiation from similar sibling tools and behavioral details that would help an agent handle errors or understand the MES integration.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 100% schema coverage, the baseline is 3. The description adds valuable semantic context by mapping the usage patterns to parameters: 'filter by status' corresponds to the status parameter and 'get specific equipment' corresponds to equipmentId, clarifying the intended use of each.

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

Purpose4/5

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

The description clearly states the verb (get), resource (equipment status), and source system (MES). However, it does not differentiate from siblings like get_assets or get_devices which may overlap conceptually.

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 second sentence implies usage patterns ('filter by status or get specific equipment'), indicating the two optional parameters are mutually exclusive modes. However, it lacks explicit guidance on when to prefer this over get_assets or get_devices.

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