Skip to main content
Glama
ogbm77

Cisco CX Cloud MCP Server

by ogbm77

get_security_advisories

Retrieve security advisories and recommendations for a specific customer to identify potential vulnerabilities and implement protective measures.

Instructions

Get security advisories for a specific customer. Returns security alerts and recommendations.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
customerIdYesThe customer ID

Implementation Reference

  • Handler for get_security_advisories tool: validates customerId, calls the /product-alerts/security-advisories API endpoint via makeApiCall, and returns the JSON response as text.
    case "get_security_advisories": {
      const customerId = args?.customerId as string;
      if (!customerId) {
        throw new Error("customerId is required");
      }
      const data = await makeApiCall("/product-alerts/security-advisories", customerId);
      return {
        content: [
          {
            type: "text",
            text: JSON.stringify(data, null, 2),
          },
        ],
      };
    }
  • Tool schema definition including name, description, and input schema requiring customerId.
    {
      name: "get_security_advisories",
      description: "Get security advisories for a specific customer. Returns security alerts and recommendations.",
      inputSchema: {
        type: "object",
        properties: {
          customerId: {
            type: "string",
            description: "The customer ID",
          },
        },
        required: ["customerId"],
      },
    },
  • src/index.ts:223-228 (registration)
    Registration of the tools list handler that exposes the get_security_advisories tool via ListTools.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      logger.debug('ListTools request received');
      return {
        tools,
      };
    });
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 the return content ('security alerts and recommendations') but doesn't describe format, pagination, rate limits, authentication requirements, or error conditions. For a data retrieval tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 concise with two sentences that directly state the tool's function and return value. There's no unnecessary information or repetition. However, it could be slightly more front-loaded by combining the two ideas more tightly.

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 has no annotations, no output schema, and a simple single-parameter input schema, the description provides basic completeness by stating what data is returned. However, it lacks details about response format, error handling, or behavioral constraints that would be helpful for an agent to use this tool effectively in context with its siblings.

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%, with the single parameter 'customerId' documented as 'The customer ID'. The description adds no additional parameter information beyond what the schema provides. According to scoring rules, when schema coverage is high (>80%), the baseline is 3 even with no param info in the description.

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 with a specific verb ('Get') and resource ('security advisories'), and specifies the scope ('for a specific customer'). It distinguishes from siblings by focusing on security advisories rather than contracts, assets, or other data types. However, it doesn't explicitly differentiate from hypothetical similar tools like 'get_all_security_advisories' or 'search_security_advisories'.

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, context for selecting this over other tools, or any exclusions. Given the sibling tools include various data retrieval functions, the agent must infer usage based on the resource name alone without explicit direction.

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/ogbm77/cisco-cx-cloud-mcp'

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