Skip to main content
Glama

Configure email identities

spur_manage_email_sender
Destructive

Create/update/delete senders, set a default, verify a sender domain, or update rotation settings. Changes affect subsequent sends. Domain credentials stay in the Spur app; no API keys or SMTP passwords are accepted here.

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is known. The description still adds real value beyond that: deferred effect on future sends and the constraint that domain credentials and SMTP/API secrets are never accepted here, which prevents a whole class of wrong invocations. It does not mention the explicit-confirmation gate, but that is documented in the schema.

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: actions first, then consequences and the credential constraint. No filler, and the most decision-relevant information is front-loaded.

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?

Covers action scope, deferred effects, and credential boundaries for a destructive multi-variant tool with no output schema. Minor gap: it does not warn that delete is irreversible or that a confirmation flag is mandatory, relying on the schema for that.

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 100% and the confirm parameter carries its own description, so the baseline is 3. The description's action list loosely mirrors the schema variants (verify, settings/rotation) but adds no format, default, or constraint detail beyond what the schema already states.

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 opens with a specific enumeration of verbs and resources: create/update/delete senders, set a default, verify a sender domain, update rotation settings. An agent knows exactly what the tool covers and can map each clause onto the oneOf action variants in the schema.

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?

It gives context that changes affect subsequent sends and implies the tool is for sender administration, but it never says when to use it versus a sibling such as spur_manage_email_domain, even though 'verify a sender domain' sits close to domain management. No explicit exclusions or prerequisites for choosing this over alternatives.

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