Skip to main content
Glama
sieteunoseis

mcp-cisco-support

search_bugs_by_product_name_affected

Search Cisco product bugs by full product name and affected software releases to identify and resolve issues in specific versions.

Instructions

Search bugs by full product name and affected releases. NOTE: Requires FULL descriptive product names (like "Cisco 4431 Integrated Services Router") not product IDs. Use search_bugs_by_product_id for product IDs like ISR4431.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
product_nameYesFull descriptive product name (e.g., "Cisco 4431 Integrated Services Router", "Cisco 2504 Wireless Controller") - NOT product IDs like ISR4431
affected_releasesYesComma-separated affected release versions (e.g., "12.5(1)SU5,14.0(1)SU2"). Can search up to 75 versions in one call.
page_indexNoPage number (10 results per page)
statusNoBug status filter. IMPORTANT: Only ONE status allowed per search. Values: O=Open, F=Fixed, T=Terminated. Do NOT use comma-separated values like "O,F".
severityNoBug severity filter. Returns bugs with ONLY the specified severity level. Values: 1=Severity 1 (highest), 2=Severity 2, 3=Severity 3, 4=Severity 4, 5=Severity 5, 6=Severity 6 (lowest). For "severity 3 or higher" bugs, use multi_severity_search tool which handles multiple separate API calls.
modified_dateNoLast modified date filter. Values: 1=Last Week, 2=Last 30 Days, 3=Last 6 Months, 4=Last Year, 5=All. Default: 5 (All)5
sort_byNoSort order for results. Default: modified_date (recent first)

Implementation Reference

  • Specific handler case in executeTool method that constructs the Cisco Bug Search API endpoint using the product_name and affected_releases parameters from tool args. Encodes parameters and sets endpoint for the makeApiCall in base class.
    case 'search_bugs_by_product_name_affected':
      endpoint = `/bugs/products/product_name/${encodeURIComponent(processedArgs.product_name)}/affected_releases/${encodeURIComponent(processedArgs.affected_releases)}`;
      break;
  • Input schema defining parameters for the tool, including required product_name and affected_releases, with descriptions and optional filters for pagination, status, severity, etc.
    inputSchema: {
      type: 'object',
      properties: {
        product_name: {
          type: 'string',
          description: 'Full descriptive product name (e.g., "Cisco 4431 Integrated Services Router", "Cisco 2504 Wireless Controller") - NOT product IDs like ISR4431'
        },
        affected_releases: {
          type: 'string',
          description: 'Comma-separated affected release versions (e.g., "12.5(1)SU5,14.0(1)SU2"). Can search up to 75 versions in one call.'
        },
        page_index: {
          type: 'integer',
          default: 1,
          description: 'Page number (10 results per page)'
        },
        status: {
          type: 'string',
          description: 'Bug status filter. IMPORTANT: Only ONE status allowed per search. Values: O=Open, F=Fixed, T=Terminated. Do NOT use comma-separated values like "O,F".',
          enum: ['O', 'F', 'T']
        },
        severity: {
          type: 'string',
          description: 'Bug severity filter. Returns bugs with ONLY the specified severity level. Values: 1=Severity 1 (highest), 2=Severity 2, 3=Severity 3, 4=Severity 4, 5=Severity 5, 6=Severity 6 (lowest). For "severity 3 or higher" bugs, use multi_severity_search tool which handles multiple separate API calls.',
          enum: ['1', '2', '3', '4', '5', '6']
        },
        modified_date: {
          type: 'string',
          description: 'Last modified date filter. Values: 1=Last Week, 2=Last 30 Days, 3=Last 6 Months, 4=Last Year, 5=All. Default: 5 (All)',
          enum: ['1', '2', '3', '4', '5'],
          default: '5'
        },
        sort_by: {
          type: 'string',
          description: 'Sort order for results. Default: modified_date (recent first)',
          enum: ['status', 'modified_date', 'severity', 'support_case_count', 'modified_date_earliest']
        },
      },
      required: ['product_name', 'affected_releases']
    }
  • Tool registration in BugApi.getTools() method, defining name, description, and inputSchema, making it available via the MCP tool interface.
    {
      name: 'search_bugs_by_product_name_affected',
      description: 'Search bugs by full product name and affected releases. NOTE: Requires FULL descriptive product names (like "Cisco 4431 Integrated Services Router") not product IDs. Use search_bugs_by_product_id for product IDs like ISR4431.',
      inputSchema: {
        type: 'object',
        properties: {
          product_name: {
            type: 'string',
            description: 'Full descriptive product name (e.g., "Cisco 4431 Integrated Services Router", "Cisco 2504 Wireless Controller") - NOT product IDs like ISR4431'
          },
          affected_releases: {
            type: 'string',
            description: 'Comma-separated affected release versions (e.g., "12.5(1)SU5,14.0(1)SU2"). Can search up to 75 versions in one call.'
          },
          page_index: {
            type: 'integer',
            default: 1,
            description: 'Page number (10 results per page)'
          },
          status: {
            type: 'string',
            description: 'Bug status filter. IMPORTANT: Only ONE status allowed per search. Values: O=Open, F=Fixed, T=Terminated. Do NOT use comma-separated values like "O,F".',
            enum: ['O', 'F', 'T']
          },
          severity: {
            type: 'string',
            description: 'Bug severity filter. Returns bugs with ONLY the specified severity level. Values: 1=Severity 1 (highest), 2=Severity 2, 3=Severity 3, 4=Severity 4, 5=Severity 5, 6=Severity 6 (lowest). For "severity 3 or higher" bugs, use multi_severity_search tool which handles multiple separate API calls.',
            enum: ['1', '2', '3', '4', '5', '6']
          },
          modified_date: {
            type: 'string',
            description: 'Last modified date filter. Values: 1=Last Week, 2=Last 30 Days, 3=Last 6 Months, 4=Last Year, 5=All. Default: 5 (All)',
            enum: ['1', '2', '3', '4', '5'],
            default: '5'
          },
          sort_by: {
            type: 'string',
            description: 'Sort order for results. Default: modified_date (recent first)',
            enum: ['status', 'modified_date', 'severity', 'support_case_count', 'modified_date_earliest']
          },
        },
        required: ['product_name', 'affected_releases']
      }
    },
  • Helper method used in executeTool to normalize affected_releases versions by removing leading zeros for Cisco API compatibility (e.g., 17.09.06 -> 17.9.6).
    private normalizeVersionString(version: string): string {
      if (!version) return version;
      // Remove leading zeros from each version segment: 17.09.06 -> 17.9.6
      return version.replace(/\.0+(\d)/g, '.$1');
    }
  • Output response type definition for Bug API tools, including bugs array with key fields and total_results.
    export interface BugApiResponse extends ApiResponse {
      bugs?: Array<{
        bug_id: string;
        headline: string;
        status: string;
        severity: string;
        last_modified_date: string;
        [key: string]: any;
      }>;
      total_results?: number;
    }
Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions a requirement for 'FULL descriptive product names' and notes the tool's limitation to 'Only ONE status allowed per search,' which adds useful context. However, it lacks details on rate limits, authentication needs, or what the response format looks like, leaving gaps for a search tool with 7 parameters.

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 concise and front-loaded, with two sentences that efficiently convey the tool's purpose and key usage guidelines. Every sentence adds value without redundancy, making it easy for an AI agent to quickly understand the tool's role.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (7 parameters, no annotations, no output schema), the description is reasonably complete. It clarifies the tool's purpose, distinguishes it from siblings, and provides usage guidelines. However, it lacks details on output format or error handling, which would be helpful for a search tool with multiple filters.

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 schema description coverage is 100%, so the schema already documents all parameters thoroughly. The description adds minimal value beyond the schema by reinforcing the product name requirement and hinting at usage constraints, but it doesn't provide additional syntax or format details. This meets the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: 'Search bugs by full product name and affected releases.' It specifies the exact resource (bugs) and filtering criteria (product name, affected releases), and distinguishes it from sibling tools like search_bugs_by_product_id and multi_severity_search by noting when to use alternatives.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use this tool versus alternatives. It states to use 'search_bugs_by_product_id for product IDs' and implies that for 'severity 3 or higher' bugs, use the 'multi_severity_search tool.' This clearly defines the tool's scope and exclusions.

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/sieteunoseis/mcp-cisco-support'

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