Skip to main content
Glama
mcp-cisco-support

mcp-cisco-support

by sieteunoseis

Assess a Cisco software upgrade

assess_upgrade
Read-only

Compare current and target Cisco product releases before upgrading to identify open bugs, target fixes, security advisories, and hardware end-of-life; defaults to Cisco's suggested release.

Instructions

Compare a current and target release for a product: open bugs on each, bugs the target fixes, and (with os_type) security advisories fixed, remaining and new; plus hardware end-of-life. Without target_version, uses Cisco's suggested release.

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": {
      "product_id": "<product_id>",
      "current_version": "<current_version>"
    },
    "name": "assess_upgrade"
  }
}

Input Schema

NameRequiredDescriptionDefault
os_typeNoOS for the security advisory comparison, e.g. "iosxe"
product_idYesBase product ID, e.g. "C9300-48P"
max_severityNoInclude open bugs of severity 1..max_severity
target_versionNoRelease to evaluate (default: Cisco suggested release)
current_versionYesRelease running today, e.g. "17.9.4"
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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds real behavioral context beyond that: the fallback to Cisco's suggested release when target_version is omitted, and the conditional gating of security advisory results on os_type. It doesn't cover data freshness, call cost, or how much data comes back, keeping it below 5.

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 dense sentence front-loads the comparison scope, then the conditional modifiers, then the fallback rule. Every clause contributes; nothing is repeated from the title or schema.

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 description carries the burden of describing results and does so by enumerating the returned sections (open bugs on each release, fixes, advisory fixed/remaining/new, hardware EOL). For a fairly complex six-parameter tool this is nearly complete; minor gaps remain on result granularity and whether comparisons are cached or live.

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 coverage is 100%, so the schema already documents all six parameters with examples. The description reinforces the os_type-to-security-advisories link and the target_version default, but adds no new meaning for max_severity or response_format beyond what the schema states. Baseline 3 applies.

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?

States a specific verb ('Compare') plus the resources (current and target release for a product) and enumerates the analysis categories produced: open bugs, fixed bugs, advisory deltas, and hardware end-of-life. This aggregate-assessment framing is clearly distinguishable from single-resource siblings like bug_search or psirt_get.

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?

Implies usage through the upgrade-assessment scenario and gives two concrete conditional rules: 'with os_type' enables security advisory comparison, and 'Without target_version, uses Cisco's suggested release.' It does not explicitly name sibling tools or state when not to use it, so a 4 rather than 5.

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