Skip to main content
Glama
Sign In
google-workspace-mcp

google-workspace-mcp

by shanebrady77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

drive_add_comment

Add a comment to a Google Drive file by supplying its file ID and the comment content. Enable team feedback without leaving your workflow.

Instructions

Add a comment to a Drive file.

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": {
      "file_id": "<file_id>",
      "content": "<content>"
    },
    "name": "drive_add_comment"
  }
}

Input Schema

NameRequiredDescriptionDefault
contentYes
file_idYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

No annotations are provided, so the description bears full responsibility for disclosure. It does not mention potential side effects, permission requirements, irreversibility, or whether the operation is a mutation, leaving the agent without critical behavioral context.

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, succinct sentence with no redundant words. It is front-loaded, directly stating the action and target, making it highly scannable.

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?

While the tool has an output schema and only two parameters, the description lacks context about file types, user permissions, or relation to other Drive tools. Combined with absent annotations and minimal parameter info, the overall context is insufficient for an agent to invoke the tool confidently.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the parameters file_id or content. The agent is left to infer from parameter titles alone, with no additional meaning provided about their format, purpose, or constraints.

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 clearly states the action ('Add a comment') and the resource ('a Drive file'), providing a specific verb and object. However, it does not explicitly distinguish itself from sibling tools like drive_list_comments, though the action difference is inherent.

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?

There is no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description simply states what it does without contextualizing its use relative to other Drive comment tools.

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