Skip to main content
Glama

Set my email preferences

set_email_preferences
Idempotent

Change your own account-wide email preferences. Provide at least one boolean: setup_reminders or task_alerts. Omitted categories are unchanged. true subscribes and false opts out. No workspace membership is required; another user's settings cannot be changed.

Input Schema

NameRequiredDescriptionDefault
task_alertsNoWhether to receive task alert emails.
setup_remindersNoWhether to receive setup reminder emails.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover safety (non-destructive, idempotent) and the description adds genuinely new behavioral facts: partial-update semantics for omitted fields, ownership restriction, and the meaning of each boolean value. This goes meaningfully beyond what the annotations declare.

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?

Four short sentences, each carrying a distinct fact: what it changes, the input requirement, merge behavior, and the ownership constraint. There is no filler and the core action leads.

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 small, non-destructive, idempotent mutation with fully documented parameters and no output schema, this covers everything an agent needs to call it correctly. Only a pointer to the sibling read tool is missing.

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

Parameters5/5

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

Schema coverage is 100% and the description still adds value by explaining the at-least-one requirement, that omitted flags are left untouched, and the subscribe/opt-out meaning of the booleans. That clarifies merge semantics the schema alone does not express.

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?

States a specific verb and resource ('Change your own account-wide email preferences') and scopes it to the caller's own account, which implicitly separates it from the sibling get_email_preferences. It stops short of naming the read counterpart, but the action and resource are unambiguous.

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?

Gives concrete invocation guidance: supply at least one boolean, omitted categories stay unchanged, true subscribes and false opts out. It also states the precondition that no workspace membership is required and that another user's settings cannot be changed, though it does not explicitly point to get_email_preferences for reading current values.

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