Skip to main content
Glama
ruegreen

Cisco MCP Pods Server

by ruegreen

update_pod_keyword

Change the password or keyword for Cisco API Gateway pods to maintain secure access and manage authentication credentials for pod management operations.

Instructions

Update the pod keyword/password record with a new value.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keywordYesNew keyword/password value (e.g., Cisco1234!)

Implementation Reference

  • Core implementation of updatePodKeyword: sends PATCH request to the pods API endpoint with the new keyword.
    async updatePodKeyword(keyword) {
      const url = `${this.baseUrl}/api/v2/pods/keyword`;
      return this.makeRequest(url, {
        method: 'PATCH',
        body: JSON.stringify({ keyword }),
      });
    }
  • Input schema definition for the update_pod_keyword tool, specifying the required 'keyword' string parameter.
    inputSchema: {
      type: 'object',
      properties: {
        keyword: {
          type: 'string',
          description: 'New keyword/password value (e.g., Cisco1234!)',
        },
      },
      required: ['keyword'],
    },
  • src/index.js:40-53 (registration)
    Registration of the update_pod_keyword tool in the stdio MCP server's tool list.
    {
      name: 'update_pod_keyword',
      description: 'Update the pod keyword/password record with a new value.',
      inputSchema: {
        type: 'object',
        properties: {
          keyword: {
            type: 'string',
            description: 'New keyword/password value (e.g., Cisco1234!)',
          },
        },
        required: ['keyword'],
      },
    },
  • src/index.js:221-231 (registration)
    MCP CallToolRequest handler case that invokes the podsClient.updatePodKeyword method.
    case 'update_pod_keyword': {
      const result = await podsClient.updatePodKeyword(args.keyword);
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify(result, null, 2),
          },
        ],
      };
    }
  • Input schema definition for the update_pod_keyword tool in the HTTP MCP server.
    inputSchema: {
      type: 'object',
      properties: {
        keyword: { type: 'string', description: 'New keyword/password value (e.g., Cisco1234!)' },
      },
      required: ['keyword'],
    },
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 this is an update operation, implying mutation, but doesn't cover critical aspects like required permissions, whether the change is reversible, potential side effects, or error conditions. For a mutation tool with zero annotation coverage, 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, efficient sentence that directly states the tool's purpose without unnecessary words. It is front-loaded with the core action and resource, making it easy to parse. Every part of the sentence contributes to understanding, achieving optimal conciseness.

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 tool's complexity as a mutation operation, lack of annotations, and absence of an output schema, the description is incomplete. It doesn't explain what the tool returns, error handling, or behavioral nuances. For a tool that modifies data, this level of detail is inadequate, leaving the agent with insufficient context for reliable use.

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 mentions updating 'with a new value', which aligns with the single parameter 'keyword' in the schema. Since schema description coverage is 100% (the parameter is well-documented with an example), the description adds minimal value beyond what the schema provides. The baseline score of 3 is appropriate as the schema does the heavy lifting for parameter semantics.

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 ('update') and the target resource ('pod keyword/password record'), making the purpose understandable. It specifies what gets updated ('with a new value'), which is specific. However, it doesn't explicitly differentiate from sibling tools like 'update_pod' or 'get_pod_keyword', leaving some ambiguity about when to choose this tool over others.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing an existing pod), exclusions, or comparisons to siblings like 'update_pod' or 'get_pod_keyword'. Without such context, an agent must infer usage from the tool name alone, which is insufficient for optimal selection.

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