Skip to main content
Glama
mcp-cisco-support

mcp-cisco-support

by sieteunoseis

Search Cisco bugs

bug_search
Read-only

Search Cisco bugs by keyword, product ID, series, or name; filter by release, severity, status, and date to find open or fixed issues.

Instructions

Search Cisco bugs by exactly one of keyword, product_id, product_series or product_name. With releases, returns bugs affecting (or fixed in) those releases. Pass several severities to search them in one call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bug_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (see paging.next_page in the result).
statusNoO = open, F = fixed, T = terminated
keywordNoKeyword(s) in the headline/description (max 50 chars)
sort_byNo
releasesNoComma-separated releases, e.g. "17.9.4,17.12.3" (leading zeros are removed). Required with product_series/product_name.
severityNoSeverities to include, e.g. ["1","2","3"]. Omit for all.
product_idNoBase product ID, e.g. "C9300-48P" or "ISR4431"
product_nameNoExact product name, e.g. "Cisco Unified Communications Manager (CallManager)"
modified_dateNoLast modified: 1 = week, 2 = 30 days, 3 = 6 months, 4 = year, 5 = all5
release_matchNoMatch bugs affecting the releases (default) or fixed in them. "fixed" works with product_series/product_name.affected
product_seriesNoFull series name, e.g. "Cisco Catalyst 9300 Series Switches"
response_formatNoconcise (default) returns key fields only; detailed adds descriptions, notes and secondary fields.concise

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered and the description need not restate it. It adds some behavioral meaning by clarifying that releases produce bugs affecting or fixed in them, but says nothing about result volume, rate limiting, or how a broad keyword search behaves against an external catalog.

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?

Three short sentences, each carrying a distinct rule, with the most important constraint (exactly one identifier) placed first. No filler or restatement of the title.

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?

For a twelve-parameter search tool with no output schema, the definition covers the combinatorial rules an agent is most likely to get wrong. Return shape is left entirely implicit (response_format is only explained in the schema), and pagination is delegated to schema descriptions, but nothing critical to a correct call is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 92%, so most parameters are self-documenting; the description's real contribution is the "exactly one of" mutual-exclusion rule, which is not encoded anywhere in the schema (required list is empty and there is no oneOf). The releases/severity sentence reinforces the relationship between two of the twelve fields. Minor gap: no hint on what happens if more than one identifier is supplied.

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?

States a specific verb and resource ("Search Cisco bugs") and immediately constrains the search to exactly one of keyword/product_id/product_series/product_name, which is far more informative than the title alone. It does not explicitly name or contrast with the sibling bug_get, so an agent must infer the search-vs-fetch split.

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

Usage Guidelines4/5

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

Gives concrete invocation guidance: use exactly one identifier type, and releases narrow results to bugs affecting or fixed in those releases. It also notes that multiple severities can be combined in one call, steering the agent away from repeated calls. It stops short of stating when to prefer a different tool or how to handle ambiguity between product_id and product_name.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.