Skip to main content
Glama
ogbm77

Cisco CX Cloud MCP Server

by ogbm77

get_hardware_inventory

Retrieve detailed hardware asset information for a specific customer account in Cisco CX Cloud to manage inventory and track equipment.

Instructions

Get hardware inventory for a specific customer. Returns details about all hardware assets.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesThe customer ID (get from get_customer_accounts first)

Implementation Reference

  • Handler for the get_hardware_inventory tool. Extracts customerId from arguments, validates it, calls the makeApiCall helper to fetch data from /inventory/hardware endpoint, and returns the JSON-formatted response.
    case "get_hardware_inventory": {
      const customerId = args?.customerId as string;
      if (!customerId) {
        throw new Error("customerId is required");
      }
      const data = await makeApiCall("/inventory/hardware", customerId);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:94-107 (registration)
    Tool registration in the tools array, including name, description, and input schema. Used by the ListTools handler to advertise the tool's availability and parameters.
    {
      name: "get_hardware_inventory",
      description: "Get hardware inventory for a specific customer. Returns details about all hardware assets.",
      inputSchema: {
        type: "object",
        properties: {
          customerId: {
            type: "string",
            description: "The customer ID (get from get_customer_accounts first)",
          },
        },
        required: ["customerId"],
      },
    },
  • Input schema definition for the get_hardware_inventory tool, specifying that a customerId string is required.
    inputSchema: {
      type: "object",
      properties: {
        customerId: {
          type: "string",
          description: "The customer ID (get from get_customer_accounts first)",
        },
      },
      required: ["customerId"],
    },
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 states the tool returns 'details about all hardware assets', which gives some behavioral insight, but lacks critical information such as whether this is a read-only operation, any rate limits, authentication needs, pagination, or error handling. The description is minimal and doesn't compensate for the absence of annotations.

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?

The description is extremely concise with two sentences that directly state the tool's function and output. It is front-loaded with the core purpose and wastes no words, making it efficient and easy to parse for an AI agent.

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?

Given the tool has no annotations, no output schema, and a simple input schema, the description is minimally adequate. It covers the basic purpose and output, but lacks details on behavior, error cases, or return format. For a tool with no structured metadata, it should provide more context to be fully helpful, but it meets the bare minimum for a simple read operation.

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?

The input schema has 100% description coverage, with the parameter 'customerId' well-documented in the schema itself. The description doesn't add any additional meaning beyond what the schema provides, such as format examples or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema handles the parameter documentation adequately.

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 tool's purpose with a specific verb ('Get') and resource ('hardware inventory'), and specifies the scope ('for a specific customer'). It distinguishes from siblings like 'get_covered_assets' or 'get_uncovered_assets' by focusing on hardware assets. However, it doesn't explicitly differentiate from all siblings, such as 'get_network_elements' which might overlap.

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 description implies usage when needing hardware inventory for a customer, and the input schema hints at prerequisites by noting 'get from get_customer_accounts first'. However, it lacks explicit guidance on when to use this tool versus alternatives like 'get_covered_assets' or 'get_uncovered_assets', and doesn't specify exclusions or detailed context.

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/ogbm77/cisco-cx-cloud-mcp'

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