Skip to main content
Glama
ruegreen

Cisco MCP Pods Server

by ruegreen

delete_pod

Remove a pod from a Cisco API Gateway collection by specifying the collection name and pod number to manage your pod inventory and resources.

Instructions

Delete a pod from a collection by its number.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
collectionYesCollection name
numberYesPod number to delete

Implementation Reference

  • Core handler function that executes the delete_pod tool logic by sending a DELETE HTTP request to the Cisco Pods API endpoint.
    async deletePod(collection, number) {
      const url = `${this.baseUrl}/api/v2/pods/${collection}/${number}`;
      return this.makeRequest(url, { method: 'DELETE' });
    }
  • Input schema definition for the delete_pod tool, specifying collection and number parameters.
    inputSchema: {
      type: 'object',
      properties: {
        collection: {
          type: 'string',
          description: 'Collection name',
        },
        number: {
          type: 'number',
          description: 'Pod number to delete',
        },
      },
      required: ['collection', 'number'],
    },
  • src/index.js:181-198 (registration)
    Tool registration in ListToolsRequestSchema handler, including name, description, and schema for delete_pod.
    {
      name: 'delete_pod',
      description: 'Delete a pod from a collection by its number.',
      inputSchema: {
        type: 'object',
        properties: {
          collection: {
            type: 'string',
            description: 'Collection name',
          },
          number: {
            type: 'number',
            description: 'Pod number to delete',
          },
        },
        required: ['collection', 'number'],
      },
    },
  • MCP CallToolRequestSchema handler case for delete_pod, which delegates to podsClient.deletePod and formats response.
    case 'delete_pod': {
      const result = await podsClient.deletePod(args.collection, args.number);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • MCP CallToolRequestSchema handler case for delete_pod in HTTP server, delegates to podsClient.deletePod.
    case 'delete_pod': {
      const result = await podsClient.deletePod(args.collection, args.number);
      return {
        content: [{ type: 'text', text: JSON.stringify(result, null, 2) }],
      };
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden but only states the basic action without disclosing critical behavioral traits. It doesn't warn that deletion is irreversible, mention permission requirements, indicate if confirmation is needed, or describe what happens to associated data. For a destructive tool, this leaves significant gaps in understanding its behavior.

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 a single, direct sentence with zero wasted words. It front-loads the core action ('Delete') and efficiently specifies the target, making it easy to parse quickly. Every word earns its place without redundancy or fluff.

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 this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It lacks information on side effects, error conditions, return values, or safety considerations. For a tool that permanently removes resources, more context is needed to use it appropriately and safely.

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 parameters are fully documented in the schema. The description adds no additional meaning beyond implying 'collection' and 'number' identify the pod to delete, which is already clear from the schema. This meets the baseline for high schema coverage without enhancing parameter understanding.

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 ('Delete') and target resource ('a pod from a collection'), making the purpose immediately understandable. However, it doesn't differentiate this destructive operation from sibling tools like 'update_pod' or 'get_pod_by_number' beyond the obvious verb difference, missing explicit contrast in scope or consequences.

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. It doesn't mention prerequisites (e.g., pod must exist), exclusions (e.g., cannot delete if in use), or suggest alternatives like 'update_pod' for modifications instead of deletion. The agent must infer usage from context alone.

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