Skip to main content
Glama
Sign In
gwagent

gwagent

by vcnngr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

gmail_spam

Moves selected Gmail conversations to Spam and reports them to Google to block unwanted messages; requires confirm=true.

Instructions

Report conversations as spam (moved to Spam; the report is sent to Google).

Requires confirm=true (outward-facing or destructive).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "gmail_spam"
  }
}

Input Schema

NameRequiredDescriptionDefault
allNoAct on EVERY conversation of the query/folder list (Gmail's 'Select all' after loading the whole list; repeated until the list is empty for actions that remove conversations from it). Needs query or folder; no index/indexes/match.
indexNoRow index from gmail.list / gmail.search (0 = first row).
matchNoSelect every row whose subject contains this text (case-insensitive).
queryNoRun this Gmail search first and take the rows from its results.
folderNoOpen this folder/label first and take the rows from it.
confirmNoMust be true: this action is outward-facing or destructive.
indexesNoSeveral row indexes (multi-selection).
max_rowsNoWith match, look at most at this many rows from the top.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that conversations are moved to Spam and that a report is sent to Google, plus the confirmation requirement. It does not mention reversibility, permission requirements, or effects on sender reputation.

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?

Two compact sentences with no waste. The core action and outcome are front-loaded, and the confirmation requirement follows immediately.

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

Completeness4/5

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

For a mutation tool with no annotations and no output schema, the description covers the essential effect and safety prerequisite. It leaves out reversibility and permission details, but the rich schema covers selection mechanics fully, making this largely sufficient.

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 description coverage is 100%, so the schema already documents all eight selection parameters in detail. The description only echoes the confirm parameter's purpose, adding the rationale that the action is outward-facing/destructive, which is marginally helpful but does not add new selection semantics.

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 states a specific verb and resource: 'Report conversations as spam,' and clarifies the outcome ('moved to Spam'). It is clearly distinct from siblings like gmail_not_spam or gmail_report_phishing, though it does not explicitly name them.

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?

It states the required prerequisite ('Requires confirm=true') and labels the action as outward-facing or destructive, which implies cautious use. However, it gives no explicit guidance on when to choose this over gmail_trash, gmail_block_sender, or gmail_report_phishing.

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