Skip to main content
Glama
mcp-cisco-support

mcp-cisco-support

by sieteunoseis

Search Cisco TAC cases

case_search
Read-only

Search Cisco TAC support cases by contract IDs or user IDs within a 90-day window. Filter by open or closed status, creation dates, and sort by status or last update.

Instructions

Find Cisco TAC cases by exactly one of contract_ids or user_ids. Cisco returns at most 90 days per search.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (see paging.next_page in the result).
sort_byNoUPDATED_DATE
user_idsNoComma-separated Cisco.com user IDs (max 10)
status_flagNoO = open, C = closed (default: both)
contract_idsNoComma-separated contract numbers (max 10)
date_created_toNoUTC, e.g. 2026-11-18T23:59:59Z
response_formatNoconcise (default) returns key fields only; detailed adds descriptions, notes and secondary fields.concise
date_created_fromNoUTC, e.g. 2026-09-01T00:00:00Z

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and external-system reach are covered. The description adds two genuinely new behavioral facts: the mutually exclusive identifier requirement and the 90-day maximum window per search, which materially shapes how an agent must chunk date ranges. It doesn't describe pagination behavior or what happens when no results match, leaving some operational detail to 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?

Two short sentences with zero filler: the selection constraint comes first and the return-range limit second. Every clause carries information an agent needs in order to call the tool correctly.

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 an 8-parameter read-only search with no output schema, the description covers the two non-obvious correctness requirements: which identifier to pass and the 90-day cap on returned data. Remaining gaps, such as how paging interacts with the 90-day window or empty-result behavior, are largely handled by the schema's page field and paging.next_page reference.

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 coverage is 88% with per-parameter descriptions for page, sort_by, status_flag, response_format and both date bounds, so the baseline is 3. The description does add the exactly-one-of constraint, which the schema does not encode (required is empty and there's no oneOf), but it doesn't explain the max-10 limits or the 90-day rule as applying to the date_created_from/to pair specifically.

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 gives a specific verb and resource ("Find Cisco TAC cases") and immediately constrains the scope to one identifier type, which separates it from a lookup-by-id sibling like case_get. It stops short of explicitly naming case_get or any other alternative, so the differentiation is implied by the search-vs-retrieve framing rather than stated.

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?

"Exactly one of contract_ids or user_ids" is a strong, actionable routing rule that tells the agent what must be supplied before calling. What's missing is guidance on when to prefer this over case_get or what to do when neither identifier is known, so it's clear but not complete.

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