Skip to main content
Glama
Sign In
Google Workspace MCP Server

Google Workspace MCP Server

by sahildhurat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

send_email

Send an email to specified recipients with subject, body, and optional cc/bcc using your Gmail account.

Instructions

Send an email immediately via the authenticated Gmail account.

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": {
      "to": "<to>",
      "subject": "<subject>",
      "body": "<body>"
    },
    "name": "send_email"
  }
}

Input Schema

NameRequiredDescriptionDefault
ccNo
toYes
bccNo
bodyYes
subjectYes
body_typeNoplain

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/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 only states 'send an email immediately', which is minimal. It lacks details on authentication requirements, rate limits, error handling, or confirmation of sending. The description is insufficient for full behavioral transparency.

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, concise sentence that front-loads the key action ('Send an email immediately'). Every word is meaningful with no redundancy.

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?

Given the tool has 6 parameters (3 required) and no output schema, the description is too brief. It does not explain return values, error states, or how to properly structure inputs like 'to' or 'body'. This incomplete context makes it harder for an agent to use the tool correctly.

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?

The schema has 0% description coverage for its 6 parameters, and the tool description provides no additional explanation for any parameter. The meaning of fields like 'body_type' or the format of email addresses is not clarified. This severely hampers correct parameter usage.

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 sends an email immediately via the authenticated Gmail account. The verb 'send' and resource 'email' are precise, and the mention of Gmail distinguishes it from siblings like 'append_to_google_doc' and 'draft_email'.

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 sending versus drafting (via 'immediately'), but does not explicitly state when to use this tool over 'draft_email' or when not to use it. No prerequisites or alternatives are mentioned.

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