Skip to main content
Glama
mcp-cisco-support

mcp-cisco-support

by sieteunoseis

Get Cisco bugs by ID

bug_get
Read-only

Retrieve Cisco bug (CDETS) details by ID for up to five bugs, with concise or detailed output, to support troubleshooting and impact assessment.

Instructions

Get Cisco bug (CDETS) details by ID, e.g. CSCwh87343. Up to 5 IDs.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "bug_ids": "<bug_ids>"
    },
    "name": "bug_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
bug_idsYesComma-separated bug IDs (max 5), e.g. "CSCwh87343,CSCvi12345"
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.6/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 agent knows this is a safe external read. The description adds only the batch limit ("Up to 5 IDs"), which is already stated in the schema, and says nothing about error behavior for invalid IDs or whether unknown IDs are skipped or fail the call.

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?

Two short sentences, front-loaded with the verb and resource, with the ID example and batch cap in the most scannable position. No filler or redundant framing.

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?

This is a simple two-parameter read tool with full schema coverage and annotations covering the safety profile, so the description is nearly sufficient. The one gap is that no output schema exists, yet the description does not characterize what "details" are returned or how they differ in shape from a search result.

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 both bug_ids and response_format are fully documented in structured fields, making 3 the baseline. The description's example ID and the max-5 reminder restate rather than extend the schema, and it says nothing about response_format that the enum description does not already cover.

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 gives a specific verb and resource ("Get Cisco bug (CDETS) details by ID") plus a concrete example identifier (CSCwh87343), so the agent knows exactly what the tool retrieves. It does not explicitly contrast itself with the sibling bug_search tool, which is the main missing piece for a 5.

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

Usage Guidelines3/5

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

The phrase "by ID" implies this is the direct-lookup path versus a search tool, and the example ID format helps the agent recognize valid input. However, there is no explicit statement of when to use this instead of bug_search or what to do when only partial identifiers are known.

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