Skip to main content
Glama

save_daily_digest_settings

Idempotent

Set whether the owner receives the Today and Tomorrow daily digest emails. Supply the preferences you want to change.

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

Input Schema

NameRequiredDescriptionDefault
todayNo
tomorrowNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this is a non-destructive, idempotent write (readOnlyHint=false, destructiveHint=false, idempotentHint=true), so the safety profile is covered. The description adds that the target is the owner's digest and that changes are selective, but it does not say whether omitted fields are left untouched, whose settings are modified, or whether changes take effect on the next send.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, with the purpose stated first and the update instruction second. There is no filler, though the second sentence is slightly vague compared to the precision of the first.

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

Completeness3/5

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

For a two-optional-boolean mutation with annotations covering the safety profile and no output schema, the definition covers the essentials. It still leaves gaps around merge semantics for omitted fields and the scope of 'owner', which matter for a settings-write tool in a large family of similar save_* settings tools.

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 0%, so the description must carry the two parameters. It does map 'today' and 'tomorrow' to the two daily digest email types and signals that both are optional via 'preferences you want to change', but it never states that the values are booleans enabling or disabling each email, nor what an omitted parameter does.

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 ('Set') and a specific resource (the owner's Today and Tomorrow daily digest email preferences), which is enough to distinguish it from the read-only sibling get_daily_digest_settings. It stops short of naming that sibling 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?

The phrase 'Supply the preferences you want to change' implies partial updates are supported and that only intended changes need be sent, which is useful usage context. However, it never says when to use this versus get_daily_digest_settings, nor whether there are prerequisites such as being the account owner.

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