Skip to main content
Glama
ogbm77

Cisco CX Cloud MCP Server

by ogbm77

get_contracts

Retrieve contract details and coverage periods for a specific customer using their customer ID to manage service agreements.

Instructions

Get all contracts for a specific customer. Returns contract details including coverage periods.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesThe customer ID

Implementation Reference

  • Handler for the 'get_contracts' tool. Validates customerId input, calls the Cisco CX Cloud API endpoint for contract details, and returns the response as formatted JSON text.
    case "get_contracts": {
      const customerId = args?.customerId as string;
      if (!customerId) {
        throw new Error("customerId is required");
      }
      const data = await makeApiCall("/contracts/contract-details", customerId);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:122-135 (registration)
    Registration of the 'get_contracts' tool in the tools list, including name, description, and input schema definition requiring 'customerId'.
    {
      name: "get_contracts",
      description: "Get all contracts for a specific customer. Returns contract details including coverage periods.",
      inputSchema: {
        type: "object",
        properties: {
          customerId: {
            type: "string",
            description: "The customer ID",
          },
        },
        required: ["customerId"],
      },
    },
  • Input schema for 'get_contracts' tool, defining the required 'customerId' string parameter.
    inputSchema: {
      type: "object",
      properties: {
        customerId: {
          type: "string",
          description: "The customer ID",
        },
      },
      required: ["customerId"],
    },
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 states the tool returns contract details including coverage periods, which is useful, but lacks critical information such as whether this is a read-only operation, potential rate limits, authentication requirements, or error handling. This leaves significant gaps for a tool that likely accesses sensitive data.

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 and front-loaded, consisting of just two sentences that directly state the tool's purpose and return value. Every word earns its place with zero waste or redundancy.

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 lack of annotations and output schema, the description is incomplete. It covers the basic purpose and return scope but misses behavioral details like safety, permissions, or response format. For a tool that likely handles sensitive contract data, this leaves the agent under-informed about critical operational aspects.

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 schema description coverage is 100%, with the single parameter 'customerId' fully documented in the schema. The description adds no additional parameter semantics beyond implying the customer context, so it meets the baseline for adequate but not exceptional value.

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 ('contracts'), and specifies the scope ('for a specific customer'). It doesn't explicitly differentiate from sibling tools like 'get_customer_accounts' or 'get_covered_assets', which prevents a perfect score.

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 provides no guidance on when to use this tool versus alternatives like 'get_customer_accounts' or 'get_covered_assets'. It mentions the customer context but offers no explicit when/when-not instructions or prerequisites, leaving usage decisions ambiguous.

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