Skip to main content
Glama

Read my email preferences

get_email_preferences
Read-onlyIdempotent

Read whether you receive setup reminders and task alerts. These settings are yours across all workspaces and are the same ones on Sinatra's email-preferences page. No workspace membership is required.

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_email_preferences"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior4/5

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

The annotations list readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, which already establish the safety profile. The description adds value on what the annotations cannot cover: the scope of the settings across all workspaces and the fact that no workspace membership is needed. It stops short of describing the exact response shape, though the two settings names give a strong hint.

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, none of them filler. The returned fields come first, scope and prerequisites follow, and the comparison with the Sinatra email-preferences page anchors the concept in a familiar UI without wasting space.

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?

There is no output schema, so the description must indicate what comes back, and naming the two settings largely does that. The remaining gap is the response format (booleans vs a nested object), but the surrounding statements about workspace scope and membership are enough for a zero-argument read tool.

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 no parameters, so the schema already has nothing to explain. This establishes the baseline of 4, and the description correctly spends no words on nonexistent arguments.

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 gives a specific verb (read) and resource (your email preferences) and names the exact settings returned: setup reminders and task alerts. It also implicitly distinguishes itself from set_email_preferences by framing the operation as a read, so an agent can pick between them without opening either schema.

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?

The context is clear: this reads the caller's own preferences, they apply across all workspaces, and no workspace membership is required. That precondition removes a common source of hesitation. It does not explicitly say when to prefer this over set_email_preferences or another account tool, but the read/write split is self-evident.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources