Skip to main content
Glama
Sign In

DataToRAG

by com.datatorag
OverviewDiscussionsAdmin

gws-mcp__gmail_untrash

Takes one Gmail message out of Trash. Takes the message ID. Returns the message ID and the labels the message carries afterwards. A message Gmail has already deleted from Trash is gone and answers as not found.

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": {
      "message_id": "<message_id>"
    },
    "name": "gws-mcp__gmail_untrash"
  }
}

Input Schema

NameRequiredDescriptionDefault
accountNoOptional email address of the connected account to use (e.g. 'user@gmail.com'). If omitted, the default account is used.
message_idYesThe ID of the message to take out of Trash.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the mutation-vs-safe-read question is answered elsewhere. The description adds genuinely useful behavior the annotations do not cover: it returns the message ID plus the labels the message carries afterwards, and it discloses that an already-permanently-deleted message comes back as not-found rather than silently succeeding.

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?

Three short sentences, each carrying distinct information: the action, the input, the return shape, and the failure mode. The action is front-loaded and there is no filler wording anywhere.

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 two-parameter mutation with no output schema, the description covers input, return value, and the not-found edge case, which is close to complete. It omits the multi-account dimension handled by the optional account parameter and does not state the precondition that the message must currently be in Trash.

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%, so both account and message_id are already documented in the schema and the baseline is 3. "Takes the message ID" restates the schema rather than adding format guidance, and the optional account parameter is not addressed in the description at all.

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?

"Takes one Gmail message out of Trash" gives a specific verb (untrash) and resource (single Gmail message), and the word "one ... message" implicitly separates it from the sibling gws-mcp__gmail_untrash_thread. It stops short of naming the thread variant explicitly, so the differentiation is inferred rather than stated.

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 only implied: an agent can infer this is the recovery counterpart to gws-mcp__gmail_trash, but the description never says "use this when a message was trashed in error" or when to prefer gws-mcp__gmail_untrash_thread for a whole conversation. No exclusions or alternatives are named.

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

All DataToRAG toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources