Skip to main content
Glama
ruegreen

Cisco MCP Pods Server

by ruegreen

get_all_pods

Retrieve all pods from a specified Cisco collection to manage and access pod information for deployment and configuration tasks.

Instructions

Get all pods from a specific collection. Works with any collection name like ciscolivepods, coelabpods, testpods, etc.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesCollection name (e.g., ciscolivepods, coelabpods, testpods)

Implementation Reference

  • Core handler function that executes the get_all_pods tool logic by making an authenticated GET request to the Pods API to retrieve all pods from the specified collection.
    async getAllPods(collection) {
      const url = `${this.baseUrl}/api/v2/pods/${collection}`;
      return this.makeRequest(url, { method: 'GET' });
    }
  • MCP CallToolRequestSchema handler case for stdio transport that invokes podsClient.getAllPods and returns the result as formatted JSON text content.
    case 'get_all_pods': {
      const result = await podsClient.getAllPods(args.collection);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
  • MCP CallToolRequestSchema handler case for HTTP transport that invokes podsClient.getAllPods and returns the result as formatted JSON text content.
    case 'get_all_pods': {
      const result = await podsClient.getAllPods(args.collection);
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
  • Tool schema definition including name, description, and input schema requiring 'collection' parameter (defined in ListToolsRequestSchema handler).
    name: 'get_all_pods',
    description: 'Get all pods from a specific collection. Works with any collection name like ciscolivepods, coelabpods, testpods, etc.',
    inputSchema: {
      type: 'object',
      properties: {
        collection: {
          type: 'string',
          description: 'Collection name (e.g., ciscolivepods, coelabpods, testpods)',
        },
      },
      required: ['collection'],
    },
  • Tool schema definition including name, description, and input schema requiring 'collection' parameter (defined in ListToolsRequestSchema handler).
    name: 'get_all_pods',
    description: 'Get all pods from a specific collection. Works with any collection name like ciscolivepods, coelabpods, testpods, etc.',
    inputSchema: {
      type: 'object',
      properties: {
        collection: { type: 'string', description: 'Collection name (e.g., ciscolivepods, coelabpods)' },
      },
      required: ['collection'],
    },
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 states the tool 'Get all pods' and works with collections, but doesn't disclose whether this is a read-only operation, if it requires authentication, rate limits, pagination behavior, or what the return format looks like (e.g., list of pod objects). For a tool with no annotation coverage, this is a significant gap in transparency.

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 concise and front-loaded with the core purpose in the first sentence. The second sentence adds useful context about collection examples without redundancy. It avoids unnecessary details, making it efficient, though it could be slightly more structured by explicitly stating the tool's scope or limitations.

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 complexity of a retrieval tool with no annotations and no output schema, the description is incomplete. It doesn't explain what 'pods' are, the format of the returned data, potential errors, or behavioral aspects like safety or performance. For a tool interacting with collections and pods, more context is needed to ensure proper agent usage.

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 description adds minimal value beyond the input schema, which has 100% coverage for the single parameter 'collection'. It provides examples of collection names ('ciscolivepods, coelabpods, testpods, etc.') that mirror the schema's description, but doesn't explain semantics like what a 'collection' represents, if there are constraints beyond being a string, or how it relates to pods. With high schema coverage, the baseline score of 3 is appropriate.

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: 'Get all pods from a specific collection.' It specifies the verb ('Get') and resource ('pods'), and distinguishes it from siblings like get_pod_by_number (which retrieves a single pod by number) and get_pod_keyword (which likely filters by keyword). However, it doesn't explicitly differentiate from other list-like operations if any exist beyond the named siblings.

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 by stating it works with 'any collection name like ciscolivepods, coelabpods, testpods, etc.,' which suggests it's for retrieving all pods from a known collection. It doesn't provide explicit guidance on when to use this tool versus alternatives like get_pod_by_number or get_pod_keyword, nor does it mention prerequisites or exclusions, leaving usage context somewhat inferred.

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