Email setup and delivery health
spur_get_email_setupRead sender identities, domain DNS/verification instructions, rotation settings, email analytics or sender stats. Free.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
spur_get_email_setupRead sender identities, domain DNS/verification instructions, rotation settings, email analytics or sender stats. Free.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two genuinely new pieces of context: the call is "Free" (no cost/credit impact) and domain sections carry DNS/verification instructions rather than raw config only. It does not state whether private or shared senders are included, nor any listing limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler; the trailing "Free." is a short, high-value qualifier. The dense "or" list is slightly harder to scan than a bulleted enumeration would be, but nothing is redundant.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only, no-output-schema dispatcher tool this covers what each section yields, which is the main selection need. It stops short of explaining the analytics date range semantics and the sender_id dependency, both of which an agent must discover by reading the oneOf branches.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The prose does loosely map sections to content (identities→senders, DNS/verification→domains, rotation→settings, analytics, sender stats), which helps pick the right enum branch, but it says nothing about the days window (default 30, max 365) or the sender_id requirement for sender/sender_stats.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb ("Read") and enumerates the concrete resources returned: sender identities, domain DNS/verification instructions, rotation settings, analytics, sender stats. This clearly separates it from mutating siblings like spur_manage_email_domain or spur_manage_email_sender, though it never names them.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The read-only framing plus "Free" implies this is the inspection path and that no changes are incurred, but there is no explicit "use this when you want to inspect, use spur_manage_* when you want to change" routing. An agent must infer the boundary from sibling names alone.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.