Skip to main content
Glama
mcp-cisco-support

mcp-cisco-support

by sieteunoseis

Get Cisco TAC cases

case_get
Read-only

Retrieve Cisco TAC support case details by case number, with concise key fields or detailed notes, owner, and contact information.

Instructions

Get Cisco TAC support cases by number. response_format "detailed" adds notes, owner and contact (one API call per case).

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": {
      "case_ids": "<case_ids>"
    },
    "name": "case_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
case_idsYesComma-separated case numbers (max 30), e.g. "701311380"
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.7/5.0
Behavior4/5

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

Annotations already cover read-only and open-world behavior, so the bar is lower, and the description still adds real operational context: 'detailed' adds notes, owner and contact, and crucially costs one API call per case. That fan-out cost is a genuine behavioral trait an agent cannot get from the annotations and matters when batching up to 30 IDs.

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 purpose, and both earn their place by adding scope and cost information. The second sentence is slightly telegraphic ('response_format "detailed" adds...') but remains clear.

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 more burden: 'concise returns key fields only' does not tell the agent which fields it actually gets, and nothing is said about error behavior for invalid or missing case numbers. The cost and detailed-mode content are covered, so it is adequate but leaves gaps on return shape.

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 100%, so the baseline is 3, and the description adds meaning beyond the schema by naming the extra content retrieved in detailed mode (owner, contact) and tying the mode to a per-case API call cost. It does not elaborate on input formatting for case_ids beyond what the schema already says.

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 Cisco TAC support cases') plus the lookup key ('by number'), which implicitly separates it from a search tool. It stops short of explicitly naming case_search as the alternative for non-numeric lookups, so sibling differentiation is inferred 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'by number' implies the caller must already have case numbers, but there is no explicit when-to-use or when-not-to-use guidance versus case_search for open-ended queries. The max-30 limit lives in the schema rather than the description, so batching strategy is only implied.

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