Skip to main content
Glama
mcp-cisco-support

mcp-cisco-support

by sieteunoseis

Get Cisco product information

product_get
Read-only

Fetches Cisco product names, series, categories, support pages, and optional MDF names for up to five product IDs, helping map IDs to support and software download resources.

Instructions

Product name, series, category and support page for product IDs. include_mdf adds the MDF (Cisco software download tree) names used by software_get.

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_ids": "<product_ids>"
    },
    "name": "product_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
include_mdfNo
product_idsYesComma-separated product IDs (max 5), e.g. "C9300-48P,ISR4431/K9"
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.5/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 adds only the side effect of include_mdf (extra MDF names relevant to software_get); it says nothing about what happens with invalid or partially resolvable product IDs, which is the main behavioral risk for a batch lookup.

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 short sentences, front-loaded with the returned fields and then the one non-obvious parameter. Nothing is redundant; the terseness borders on under-specification but no sentence 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?

With no output schema, the description does list the returned fields, which is the essential missing piece. For a low-complexity 3-parameter lookup, though, it should also mention behavior for unresolvable IDs (omitted vs error) and that response_format controls detail level, which only the schema covers.

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 67%: product_ids (with the max-5 rule and an example) and response_format are documented in the schema, while include_mdf has no schema description. The description fills exactly that gap by explaining that include_mdf pulls in MDF/Cisco software download tree names, adding real meaning beyond the structured fields.

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 (product IDs) and enumerates exactly what comes back: name, series, category and support page, which lets an agent distinguish this lookup from software_get, bug_get or eox_get. The verb is implied rather than stated, but the field list is specific enough that the tool's role is unambiguous.

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?

There is an implicit workflow hint: include_mdf yields the MDF names 'used by software_get', so the agent can infer this call feeds a follow-up software_get. However, it never states when to choose product_get over alternatives such as device_lookup, nor any prerequisites, so guidance remains implied rather than explicit.

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