Skip to main content
Glama

save_email_settings

Save sender, reply-to and footer defaults for future campaign emails. Read the current settings revision before saving.

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": {
      "revision": "<revision>",
      "value": "<value>"
    },
    "name": "save_email_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
revisionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent write, so the safety profile is covered. The description adds the meaningful concurrency trait that a revision must be read first, but it does not say what happens when the revision is stale, nor whether all fields are overwritten wholesale.

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 tight sentences with zero filler, and the functional summary is front-loaded ahead of the precondition. Every clause carries actionable information.

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?

With no output schema and no parameter descriptions, the description must carry the burden, and it does cover the core write plus the revision requirement. It leaves gaps around the flattened footer fields and what a successful save returns or changes for in-flight drafts.

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% across two top-level params, one of which is a nested object with six undocumented fields. The description compensates partially by grouping sender, reply-to and footer (postal/business) concepts and flagging the revision parameter's purpose, but it says nothing about hideCockatooBranding or the overwrite semantics of the value object.

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 ('Save') and resource ('sender, reply-to and footer defaults for future campaign emails'), making the scope of the write clear. It does not explicitly name the read counterpart among siblings (e.g., get_email_settings), so sibling differentiation is only implied via the revision precondition.

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?

It gives a concrete usage precondition: 'Read the current settings revision before saving,' which tells an agent this is a two-step read-then-write flow. There is no explicit statement of when NOT to use it or a named alternative tool, keeping it short of a 5.

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