Skip to main content
Glama
gmail-mcp
by gchallen

get_profile

Read-only

Retrieve the authenticated Gmail account's email address, message and thread counts, and current history ID to identify whose mailbox is connected.

Instructions

The authenticated account: email address, total message and thread counts, current history ID. Use it to learn whose mailbox this is.

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": "get_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.9.2

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds the concrete payload fields, which is genuinely useful given there is no output schema, but it says nothing about authentication requirements, scope/permissions needed, or whether counts are approximate or live.

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 sentences, both earning their place: the first lists the returned data, the second states the intended use. It is front-loaded and contains no filler or restatement of the tool name.

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 no-parameter, read-only identity lookup with no output schema, the description covers the essential return fields an agent needs to decide whether to call it. It stops short of noting freshness of counts or any permission scope, but nothing required for correct invocation is missing.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4; there is no parameter semantics to explain and the schema is empty and fully described. Nothing in the description misrepresents the call signature.

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 names the resource concretely ('the authenticated account') and enumerates exactly what is returned: email address, message and thread counts, history ID. That is enough to distinguish it from the sibling tools, which all operate on messages, threads, drafts, labels, or attachments, though it doesn't explicitly say so.

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

Usage Guidelines4/5

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

'Use it to learn whose mailbox this is' gives an explicit use case and clear context for invoking the tool. There are no exclusion rules or named alternatives, but with zero parameters and an unambiguous scope, there is little ambiguity to resolve.

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