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'],
    },

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