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

cloud-support-mcp

by polar3130
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list_case_attachments

Retrieve a paginated list of attachments for a Google Cloud support case. Specify the case name to access associated files.

Instructions

List all attachments associated with a support 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": {
      "parent": "<parent>"
    },
    "name": "list_case_attachments"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentYesThe name of the case for which attachments should be listed (e.g., projects/{project_id}/cases/{case_id} or organizations/{org_id}/cases/{case_id})
pageSizeNoMaximum number of attachments to return (default: 10, max: 100)
pageTokenNoToken for pagination

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.2

TDQS

B3.4/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 disclose behavioral traits. It does not mention pagination (despite the pageSize/pageToken parameters), return format, or any access requirements. The phrase 'List all attachments' could mislead given pagination limits. This is a significant gap for a tool with no annotation support.

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 is a single, front-loaded sentence that states the core purpose without any fluff. Every word earns its place, making it highly concise and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description should clearly explain what the tool returns and how it behaves. It does not mention that results are paginated or what data is included for each attachment. For a simple tool this may be minimally viable, but it leaves important context 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 coverage is 100%, and each parameter has a descriptive comment with examples and constraints (e.g., parent path format, pageSize max). The description adds no further semantic value beyond what the schema already provides, so a baseline of 3 is appropriate.

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 uses a specific verb ('List') and clearly identifies the resource ('attachments') and the scope ('associated with a support case'). It unambiguously distinguishes this tool from siblings like list_support_cases (lists cases) and get_case_comments (gets comments).

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?

Usage is implied by the tool's name and description: you use this when you need attachments for a case. However, there is no explicit guidance about when to prefer this over alternatives, nor any mention of prerequisites or exclusions, so it falls to implied usage rather than clear context.

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