Skip to main content
Glama
Sign In
mcp-cisco-support

mcp-cisco-support

by sieteunoseis
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_case_summary

Retrieve brief summaries for up to 30 Cisco support case IDs, including status and severity information.

Instructions

Get case summary information for up to 30 specific case IDs. Returns brief information for multiple cases.

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

Input Schema

NameRequiredDescriptionDefault
sort_byNoSort results by field. UPDATED_DATE: Sort by last modification time (ascending). Default. STATUS: Sort by status (ascending)UPDATED_DATE
case_idsYesComma-separated list of case IDs (max 30, e.g., "123456789,987654321")

Schema Changelog

Changes observed during successful MCP inspections.

  1. Removedv1.11.1
  2. Addedv1.8.1
  3. Removedv1.7.0
  4. Addedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must carry the full transparency burden. It only states 'Returns brief information' without disclosing what fields are included, whether authentication is required, rate limits, or any side effects. This significant gap leaves the agent uninformed about critical behavioral traits.

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?

The description consists of two clear, front-loaded sentences with zero extraneous information. Every word contributes to conveying the tool's function and constraint.

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?

Given the absence of an output schema, the description should elaborate on what 'brief information' includes. It does not, leaving the agent uncertain about the return format. However, the core functionality and constraints (max 30 IDs) are conveyed, so completeness is adequate but not thorough.

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?

The input schema already describes both parameters with 100% coverage, including the max count for case_ids and enumeration for sort_by. The description adds no additional semantic value beyond the tool's purpose, warranting the baseline score of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

The description clearly states the verb 'Get', the resource 'case summary information', and the scope 'up to 30 specific case IDs' for multiple cases. This distinguishes it from siblings like 'get_case_details' which presumably returns full details for a single case.

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 description implies usage for obtaining summaries of multiple cases by ID, but does not explicitly state when to use this tool versus alternatives (e.g., get_case_details for full details, search_cases_by_user for user-based queries). No exclusions or when-not guidance is provided.

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

Deploy Server

Other Tools