Skip to main content
Glama
ogbm77

Cisco CX Cloud MCP Server

by ogbm77

get_customer_accounts

Retrieve accessible customer accounts and IDs from Cisco CX Cloud to enable subsequent operations like inventory queries and contract management.

Instructions

Get all accessible CX Cloud customer accounts and their IDs. Use this first to get customer IDs for other operations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The switch case handler for the 'get_customer_accounts' tool. It calls makeApiCall to the '/customer-info/customer-details' endpoint and returns the JSON-formatted response as text content.
    case "get_customer_accounts": {
      const data = await makeApiCall("/customer-info/customer-details");
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • src/index.ts:86-93 (registration)
    Registration of the 'get_customer_accounts' tool in the tools array provided to the listTools handler. Includes name, description, and empty input schema (no parameters required).
    {
      name: "get_customer_accounts",
      description: "Get all accessible CX Cloud customer accounts and their IDs. Use this first to get customer IDs for other operations.",
      inputSchema: {
        type: "object",
        properties: {},
      },
    },
  • Input schema for the 'get_customer_accounts' tool, defining an empty object (no input parameters required).
    inputSchema: {
      type: "object",
      properties: {},
    },
Behavior3/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 retrieves 'all accessible' accounts, which implies a read-only operation without destructive effects, but lacks details on permissions, rate limits, pagination, or response format. It adds some context about accessibility but misses key behavioral traits.

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 two sentences, front-loaded with the core purpose and followed by usage guidance. Every word earns its place with no redundancy or fluff, making it highly efficient and well-structured.

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 no annotations and no output schema, the description is incomplete for a tool that likely returns a list of accounts. It explains the purpose and usage but omits details on response format, error handling, or data scope (e.g., what 'accessible' means). For a read operation with zero structured metadata, more context would be helpful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has 0 parameters, and schema description coverage is 100%, so no parameter documentation is needed. The description doesn't add param info beyond the schema, but with no params, a baseline of 4 is appropriate as there's nothing to compensate for.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('all accessible CX Cloud customer accounts and their IDs'), making the purpose specific and unambiguous. It distinguishes this tool from siblings by focusing on customer accounts rather than contracts, assets, or other entities.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly provides usage guidance: 'Use this first to get customer IDs for other operations.' This tells the agent when to use this tool (as an initial step) and implies its role in a workflow, though it doesn't name specific alternatives.

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