Skip to main content
Glama
mcp-cisco-support

mcp-cisco-support

by sieteunoseis

Get Cisco end-of-life dates

eox_get
Read-only

Retrieve Cisco end-of-sale and end-of-support dates by product ID, serial number, software release, or announcement date range to assess lifecycle status and plan upgrades.

Instructions

End-of-sale / end-of-support dates by exactly one of product_ids, serial_numbers, software_releases, or an announcement date range (start_date + end_date).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (see paging.next_page in the result).
end_dateNoYYYY-MM-DD
page_sizeNoRecords per page for software_releases and date lookups
start_dateNoYYYY-MM-DD, EoX announcements from this date
product_idsNoComma-separated product IDs (max 20), e.g. "VG224,C9300-48P"
serial_numbersNoComma-separated serial numbers (max 20)
response_formatNoconcise (default) returns key fields only; detailed adds descriptions, notes and secondary fields.concise
software_releasesNoSemicolon-separated "version,OS" pairs (max 20), e.g. "15.4(3)M,IOS;17.9.4,IOS-XE"

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.7/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's contribution is the mutual-exclusivity constraint, which is genuinely non-obvious because the schema marks nothing required. It does not mention bulk limits or that paging only applies to certain selectors, both of which matter operationally.

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, leading with the payload returned before the selector constraint. Nothing could be removed without losing information.

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 carries some burden for return values; it names the date types returned but says nothing about result shape, per-mode pagination behavior, or what happens when a selector matches nothing. Given an 8-parameter read tool with fully documented params, this is adequate but leaves real gaps.

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 per-parameter meaning (formats, max 20 items, concise vs detailed) is already fully documented and the baseline of 3 applies. The description's only addition is that the four selectors are alternatives rather than combinable, which is useful but not per-parameter detail.

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?

Names the exact resource returned (end-of-sale / end-of-support dates) and the four mutually exclusive selector types, so an agent knows precisely what this fetches versus case_get, bug_get or psirt_get. It stops short of 5 because the description is a verbless noun phrase and never explicitly contrasts itself with a named sibling.

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 'exactly one of' phrasing successfully rules out combining selectors, which is real usage guidance the schema does not encode (required params = 0). However, there is no advice on which selector to prefer when multiple are available, and no signal about when to reach for eox_get over software_get or product_get.

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