cloud-support-mcp

get_case_comments

Retrieve comments and conversation history for a specific Google Cloud support case by providing its resource name.

Instructions

Get comments and conversation history for a specific 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": {
      "name": "<name>"
    },
    "name": "get_case_comments"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	The full resource name of the case (e.g., projects/{project_id}/cases/{case_id})

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.2Aug 2, 2026

TDQS

B3.3/5.0

Behavior2/5

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

With no annotations and no output schema, the description carries the full burden of behavioral disclosure. It only states the action ('Get') without detailing pagination, ordering, permissions, or whether the conversation history includes private/internal comments. This is a minimal read operation disclosure but lacks richness expected 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 conveys the essential purpose without unnecessary detail. Every word earns its place, making it maximally concise.

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?

For a simple one-parameter fetch tool, the description is adequate but incomplete. It does not specify the return format or any edge cases, and since there is no output schema, the agent must guess what 'comments and conversation history' includes. The lack of annotations increases the burden, so a 3 reflects a minimum viable description.

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 schema provides 100% coverage for the single 'name' parameter with a clear format example. The description adds no parameter-specific meaning beyond restating the scope ('for a specific support case'), so the baseline score 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 clearly states the tool retrieves 'comments and conversation history' for a specific support case, using a specific verb ('Get') and resource ('comments and conversation history'). It distinguishes itself from siblings like get_support_case (case details) and create_case_comment (creation).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The description implies the tool is for retrieving comments for a case but provides no explicit guidance on when to use it versus alternatives like get_support_case or search_support_cases. There is no mention of prerequisites or exclusions, leaving the agent to infer usage from the name alone.

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

Deploy Server