Skip to main content
Glama
AnuwatThisuka

CMMS MCP Server

get_assets

Retrieve assets from a CMMS system, filtering by operational status or fetching specific assets by ID to manage manufacturing operations and maintenance tasks.

Instructions

Get assets from CMMS system. Can filter by status or get specific asset.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoFilter by asset status
assetIdNoGet specific asset by ID

Implementation Reference

  • The handleGetAssets method executes the logic for the get_assets tool, filtering mock assets by ID or status.
    private handleGetAssets(args: { status?: string; assetId?: string }) {
      let assets = [...mockAssets];
    
      if (args.assetId) {
        assets = assets.filter((a) => a.id === args.assetId);
      } else if (args.status) {
        assets = assets.filter((a) => a.status === args.status);
      }
    
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(assets, null, 2),
          },
        ],
      };
  • src/index.ts:159-174 (registration)
    The tool definition for get_assets in the MCP listTools handler.
    name: "get_assets",
    description:
      "Get assets from CMMS system. Can filter by status or get specific asset.",
    inputSchema: {
      type: "object",
      properties: {
        status: {
          type: "string",
          enum: [
            "operational",
            "maintenance",
            "out-of-service",
            "retired",
          ],
          description: "Filter by asset status",
        },
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. It lacks information about pagination, what happens when both parameters are provided, authentication requirements, error handling, or the structure of returned assets.

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 redundancy. The first establishes system context (CMMS) and action; the second summarizes parameter capabilities. Every sentence earns its place, though brevity comes at the cost of completeness given missing annotations.

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 complexity of the CMMS domain (evidenced by numerous sibling tools for equipment, devices, sensors, and work orders) and the absence of annotations or output schema, the description should clarify what constitutes an 'asset' and how it relates to similar entities. It does not.

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%, establishing a baseline of 3. The description adds marginal value by implying an 'or' relationship between filtering by status versus retrieving a specific assetId, suggesting alternative usage modes not explicitly stated in the schema constraints.

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?

The description states 'Get assets from CMMS system,' providing a clear verb and resource with system context. However, it fails to distinguish 'assets' from sibling tools like get_equipment, get_devices, or get_sensors, which appear to serve similar functions in the CMMS domain.

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 capabilities ('Can filter by status or get specific asset') but provides no guidance on when to use this tool versus alternatives like get_equipment or get_devices, nor does it indicate prerequisites or mutual exclusivity of parameters.

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