Skip to main content
Glama
mcp-cisco-support

mcp-cisco-support

by sieteunoseis

Get Cisco RMAs

rma_get
Read-only

Retrieve a Cisco return (RMA) by RMA number or list RMAs for a Cisco.com user ID, optionally filtered by date and status.

Instructions

Get a Cisco RMA (return) by rma_number, or list RMAs for a Cisco.com user_id (optionally filtered by date and status).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (see paging.next_page in the result).
statusNo
to_dateNouser_id search: YYYY-MM-DD
user_idNoCisco.com user ID
from_dateNouser_id search: YYYY-MM-DD (max 90-day range)
rma_numberNoe.g. "804891407"
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.9/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 the two-mode behavior but says nothing about pagination, the 90-day range limit, or permissions — the 90-day cap only appears in the schema.

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 well-formed sentence that front-loads the two modes and appends filters as a subordinate clause. No filler and nothing redundant with the 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?

For a 7-parameter, zero-required read tool with no output schema, the description covers the main behavioral fork. Minor gaps remain: behavior when no selector is provided and any list-size limits, but the rich schema covers most parameter detail.

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 86%, so the baseline is 3; the description earns a point by linking rma_number to single-record lookup and user_id to list mode, a relationship the flat schema does not make explicit. It does not explain the page or response_format semantics beyond what the schema states.

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?

States a specific verb and resource (get a Cisco RMA / list RMAs) and names the two addressing keys, rma_number and user_id. It clearly conveys that the tool serves both single-fetch and list modes, though it doesn't explicitly distinguish itself from the *_get / *_search siblings.

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?

The 'X by rma_number, or list ... for user_id' construction tells the agent which selector to supply for which outcome, and the 'optionally filtered by date and status' clause signals filters are secondary. It stops short of stating mutual exclusivity or what happens if both/no selectors are supplied.

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