Skip to main content
Glama
mcp-cisco-support

mcp-cisco-support

by sieteunoseis

Look up Cisco devices by serial number

device_lookup
Read-only

Retrieve contract coverage, warranty, product details, and end-of-life dates for up to 20 Cisco serial numbers in one call.

Instructions

For each serial number: contract coverage and warranty, product details, and end-of-life dates, in one call. Up to 20 serials.

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": {
      "serial_numbers": "<serial_numbers>"
    },
    "name": "device_lookup"
  }
}

Input Schema

NameRequiredDescriptionDefault
includeNoSections to include (default: all)
serial_numbersYesComma-separated serial numbers (max 20), e.g. "FJC29161RHS,FTX1917AJJU"
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 safety profile is covered. The description adds that all three data sections arrive in a single call and restates the 20-serial cap, but that cap is also in the schema, and it says nothing about partial failures, missing serials, or rate limits for a bulk lookup.

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 payload contents and followed by the cardinality limit. There is no filler, and the redundant serial cap is a cheap reinforcement rather than bloat.

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 three fully documented parameters, no output schema, and read-only annotations, the description covers what an agent needs: what comes back, for how many serials, and in one request. Only the handling of unknown serials or per-serial errors is left unstated.

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 the schema already documents serial_numbers, include, and response_format fully. The description's enumeration of coverage/product/eox loosely mirrors the include enum but adds no syntax, ordering, or behavior detail 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and enumerates exactly what is returned per serial: contract coverage and warranty, product details, and end-of-life dates. The phrase "in one call" implicitly distinguishes it from the single-purpose siblings (eox_get, product_get), but it never names an alternative outright, so the differentiation is suggestive rather than explicit.

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?

Usage is only implied: the batch framing ("For each serial number" ... "Up to 20 serials") signals this is the bulk path for serial-based lookups. There is no explicit statement of when to prefer it over eox_get/product_get for a single device, and no exclusions or prerequisites are given.

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