Skip to main content
Glama
mcp-cisco-support

mcp-cisco-support

by sieteunoseis

Get a Cisco security advisory

psirt_get
Read-only

Retrieve Cisco PSIRT security advisory details using exactly one advisory ID, CVE, or bug ID to assess vulnerability impact and remediation guidance.

Instructions

Get Cisco PSIRT security advisories by exactly one of advisory_id, cve or bug_id.

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": "psirt_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
cveNoe.g. "CVE-2023-20198"
bug_idNoe.g. "CSCwh87343"
advisory_idNoe.g. "cisco-sa-iosxe-webui-privesc-j22SaA4z"
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.7/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. The description contributes the non-obvious exclusivity rule (exactly one identifier), which is real behavioral context. It does not describe error behavior when zero or multiple identifiers are supplied, nor anything about the advisory payload returned.

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?

A single sentence with zero filler, front-loading the operation and immediately following with the input constraint an agent needs before calling.

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?

With no output schema, the definition plus annotations cover what the tool fetches, the identifier formats (via schema examples), the output verbosity control, and the one-identifier rule. It is nearly complete; only the failure mode for zero or multiple identifiers is left unstated.

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 100%, so the baseline would be 3, but the description adds meaning the schema does not express: the schema lists no required fields and no oneOf/anyOf constraint, so 'exactly one of advisory_id, cve or bug_id' is genuinely new information about parameter interaction. It adds nothing beyond the schema for response_format, which is already fully documented.

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 ('Get Cisco PSIRT security advisories') and adds the key scoping detail that lookup is by exactly one identifier. That implicitly separates it from psirt_search, but it never names the sibling or any other alternative, so sibling differentiation is only inferred.

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 exactly one of advisory_id, cve or bug_id' tells an agent what kind of input is expected (an exact identifier rather than keywords), which implies when to use it over a search tool. There is no explicit when-to-use/when-not statement and no named alternative, so usage guidance remains implied rather than stated.

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