Skip to main content
Glama
AnuwatThisuka

CMMS MCP Server

get_production_orders

Retrieve production orders from MES systems with optional filtering by status or order ID to track manufacturing workflow progress.

Instructions

Get production orders from MES system. Can filter by status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by production order status
orderIdNoGet specific production order by ID

Implementation Reference

  • Handler for 'get_production_orders' which processes incoming requests, filters mock production order data based on ID or status, and returns the result.
    private handleGetProductionOrders(args: {
      status?: string;
      orderId?: string;
    }) {
      let orders = [...mockProductionOrders];
    
      if (args.orderId) {
        orders = orders.filter((o) => o.id === args.orderId);
      } else if (args.status) {
        orders = orders.filter((o) => o.status === args.status);
      }
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(orders, null, 2),
          },
        ],
      };
    }
  • src/index.ts:65-83 (registration)
    Tool registration for 'get_production_orders' in the listTools request handler, including its input schema.
    {
      name: "get_production_orders",
      description:
        "Get production orders from MES system. Can filter by status.",
      inputSchema: {
        type: "object",
        properties: {
          status: {
            type: "string",
            enum: ["planned", "in-progress", "completed", "cancelled"],
            description: "Filter by production order status",
          },
          orderId: {
            type: "string",
            description: "Get specific production order by ID",
          },
        },
      },
    },
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to deliver. It does not indicate whether the operation returns a list or single object, pagination behavior, rate limits, or authentication requirements. The word 'Get' implies read-only access but lacks explicit confirmation of safety.

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 consists of two efficient sentences with no filler. The first sentence establishes the core purpose and system context, while the second highlights key functionality. It avoids tautology and wastes no words, though it could sacrifice some brevity for additional behavioral context.

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?

Given the absence of annotations and output schema, the description should explain expected return values, pagination, and differentiate from similar siblings like 'get_work_orders'. It mentions 'MES system' (Manufacturing Execution System) which provides domain context, but remains incomplete regarding behavioral traits and tool selection criteria.

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 mentions status filtering which aligns with the schema, but does not add syntax details, format examples, or explain the relationship between the optional 'orderId' (specific lookup) and 'status' (filtering) parameters 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?

The description clearly identifies the action ('Get'), resource ('production orders'), and source system ('MES system'). However, it loses a point for failing to distinguish from the similar sibling tool 'get_work_orders', which could cause selection ambiguity in a manufacturing context where production orders and work orders are distinct concepts.

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?

The description mentions filtering capability ('Can filter by status') but provides no explicit guidance on when to use this tool versus alternatives like 'get_work_orders', nor does it specify prerequisites or conditions where this tool should be preferred over other retrieval tools in the sibling list.

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