Skip to main content
Glama
mcp-cisco-support

mcp-cisco-support

by sieteunoseis

Get Cisco software recommendations

software_get
Read-only

Retrieve Cisco-recommended software, available releases, or releases compatible with a product using product or MDF IDs, optionally filtered by current release.

Instructions

Cisco suggested software for products. view: "suggested" (Cisco-recommended releases, default), "releases" (latest releases), or "compatible" (releases compatible with one product, optionally from current_release).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (see paging.next_page in the result).
viewNosuggested
mdf_idsNoComma-separated MDF IDs (from product_get include_mdf or a previous software_get)
product_idsNoComma-separated product IDs (max 10; 1 for compatible), e.g. "C9300-48P"
current_imageNocompatible view: the image file running today
current_releaseNocompatible view: the release running today
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

B3.3/5.0
Behavior2/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 adds nothing beyond that: no word on result shape, paging behavior, rate limits, or what happens when a view/product combination yields nothing. For a query tool whose output is not schema-documented, it leaves behavior almost entirely to inference.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two compact sentences that front-load the resource and then enumerate the mode selector, with no filler. The phrasing is terse to the point of being telegraphic ('Cisco suggested software for products.'), but nothing is wasted.

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

Completeness3/5

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

For a 7-parameter, zero-required tool with no output schema, the description covers the mode dimension but says nothing about the paginated nature of results or the concise/detailed distinction that determines what comes back. The schema carries most of the remaining weight, leaving this adequate but not complete.

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 description coverage is high (86%), which sets the baseline at 3, and the description earns an upgrade by explaining the 'view' enum values that the schema lists without any per-value description — including what 'compatible' scopes to and its interaction with current_release. It does not touch page, response_format, or current_image, but those are documented in the schema.

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 names the resource (Cisco software recommendations for products) and immediately characterizes three retrieval modes, so an agent knows this is a software-version lookup rather than a product, bug, or EoX lookup. It stops short of explicitly distinguishing itself from near-neighbors like assess_upgrade or product_get, and the opening is a noun phrase with no verb.

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 three view values are explained well enough to select a mode, including the note that 'compatible' works for one product and can be narrowed by current_release. However, there is no guidance on when to reach for this tool versus product_get or assess_upgrade, and no stated preconditions such as needing product_ids before calling.

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