Skip to main content
Glama
AnuwatThisuka

CMMS MCP Server

get_maintenance_tasks

Retrieve maintenance tasks from a CMMS system with filters for status, priority, type, or asset to manage work orders and track repairs.

Instructions

Get maintenance tasks from CMMS system. Can filter by status, priority, or type.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by task status
priorityNoFilter by priority
taskTypeNoFilter by task type
assetIdNoFilter by asset ID

Implementation Reference

  • The implementation of the get_maintenance_tasks tool handler.
    private handleGetMaintenanceTasks(args: {
      status?: string;
      priority?: string;
      taskType?: string;
      assetId?: string;
    }) {
      let tasks = [...mockMaintenanceTasks];
    
      if (args.assetId) {
        tasks = tasks.filter((t) => t.assetId === args.assetId);
      }
      if (args.status) {
        tasks = tasks.filter((t) => t.status === args.status);
      }
      if (args.priority) {
        tasks = tasks.filter((t) => t.priority === args.priority);
      }
      if (args.taskType) {
        tasks = tasks.filter((t) => t.taskType === args.taskType);
      }
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(tasks, null, 2),
          },
  • src/index.ts:123-146 (registration)
    Registration of the get_maintenance_tasks tool including its schema definition.
    {
      name: "get_maintenance_tasks",
      description:
        "Get maintenance tasks from CMMS system. Can filter by status, priority, or type.",
      inputSchema: {
        type: "object",
        properties: {
          status: {
            type: "string",
            enum: [
              "scheduled",
              "in-progress",
              "completed",
              "cancelled",
              "overdue",
            ],
            description: "Filter by task status",
          },
          priority: {
            type: "string",
            enum: ["low", "medium", "high", "critical"],
            description: "Filter by priority",
          },
          taskType: {
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure but offers minimal details. It does not specify pagination behavior, what fields are returned, or the effect of calling without filters (return all tasks?).

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 two-sentence structure is appropriately brief and front-loaded with the core purpose. However, it is incomplete in that it fails to mention the 'assetId' filter parameter available in the schema.

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 retrieval operation with well-documented schema parameters, but lacks critical context regarding the relationship between maintenance tasks, work orders, and maintenance history, which is essential for correct tool selection given the sibling set.

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 description coverage is 100%, establishing a baseline of 3. The description enumerates three filters (status, priority, type) but omits 'assetId', adding no semantic depth beyond what the schema already provides.

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?

Clearly states the action ('Get') and resource ('maintenance tasks') with source context ('CMMS system'). However, it does not distinguish from sibling tools like 'get_maintenance_history' or 'get_work_orders', which appear to retrieve similar operational data.

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?

Provides no guidance on when to use this tool versus alternatives like 'get_work_orders' or 'get_maintenance_history', nor does it mention prerequisites or rate limiting. The agent must infer usage from the resource name alone.

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