Skip to main content
Glama
ruegreen

Cisco MCP Pods Server

by ruegreen

get_pod_by_number

Retrieve detailed pod information by specifying its number within a collection, including login credentials, phone numbers, and current operational status.

Instructions

Get a specific pod by its number from a collection. Returns pod details including login credentials, phone numbers, and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesCollection name (e.g., ciscolivepods)
numberYesPod number (e.g., 1, 2, 3)

Implementation Reference

  • Core handler function that executes the tool logic by constructing the API endpoint URL and making a GET request via the makeRequest helper.
    async getPodByNumber(collection, number) {
      const url = `${this.baseUrl}/api/v2/pods/${collection}/${number}`;
      return this.makeRequest(url, { method: 'GET' });
    }
  • Input schema definition for the get_pod_by_number tool, specifying collection (string) and number (number) as required parameters.
    name: 'get_pod_by_number',
    description: 'Get a specific pod by its number from a collection. Returns pod details including login credentials, phone numbers, and status.',
    inputSchema: {
      type: 'object',
      properties: {
        collection: {
          type: 'string',
          description: 'Collection name (e.g., ciscolivepods)',
        },
        number: {
          type: 'number',
          description: 'Pod number (e.g., 1, 2, 3)',
        },
      },
      required: ['collection', 'number'],
    },
  • src/index.js:245-255 (registration)
    Tool registration and dispatcher in the CallToolRequestSchema handler for the stdio server, which invokes the handler and formats the response.
    case 'get_pod_by_number': {
      const result = await podsClient.getPodByNumber(args.collection, args.number);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Tool registration and dispatcher in the CallToolRequestSchema handler for the HTTP server, invoking the handler and returning formatted content.
    case 'get_pod_by_number': {
      const result = await podsClient.getPodByNumber(args.collection, args.number);
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
    }
  • Input schema definition for the get_pod_by_number tool in the HTTP server, with collection and number parameters.
    name: 'get_pod_by_number',
    description: 'Get a specific pod by its number from a collection.',
    inputSchema: {
      type: 'object',
      properties: {
        collection: { type: 'string', description: 'Collection name' },
        number: { type: 'number', description: 'Pod number' },
      },
      required: ['collection', 'number'],
    },
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 of behavioral disclosure. It mentions that the tool returns pod details including login credentials, phone numbers, and status, which adds some context about sensitive data. However, it lacks critical behavioral traits such as whether this is a read-only operation, authentication requirements, error handling, or rate limits, leaving significant gaps for a mutation-free tool.

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 is appropriately sized with two sentences that are front-loaded: the first states the purpose, and the second specifies return details. There is minimal waste, though it could be slightly more structured by explicitly separating purpose from output.

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's moderate complexity (2 parameters, no output schema, no annotations), the description is minimally adequate. It covers the purpose and return details but lacks information on usage guidelines, behavioral traits, and error handling. With no output schema, it should ideally explain return values more thoroughly, but it provides a basic overview.

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%, so the input schema already fully documents both parameters (collection and number) with descriptions and types. The description adds no additional meaning beyond what the schema provides, such as examples or constraints, resulting in the baseline score of 3.

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 action ('Get a specific pod by its number') and resource ('from a collection'), with specific return details mentioned. However, it doesn't explicitly distinguish this tool from sibling tools like 'get_pod_keyword' or 'get_all_pods', which would require sibling differentiation for a score of 5.

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?

No guidance is provided on when to use this tool versus alternatives like 'get_pod_keyword' (which might fetch by keyword instead of number) or 'get_all_pods' (which retrieves all pods). The description implies usage for retrieving a specific pod by number but offers no explicit context or exclusions.

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/ruegreen/CiscoMCPPods'

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