Skip to main content
Glama

Connect and verify sending domains

spur_manage_email_domain
Destructive

Create/update a sending domain and return DNS instructions, verify DNS records, or delete a custom domain. No email is sent. If credentials are required, complete that step in Spur settings.

Input Schema

NameRequiredDescriptionDefault

No arguments

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 destructiveHint=true, non-idempotent, and open-world, so the safety profile is known. The description adds genuinely useful context — that DNS instructions are returned and that 'No email is sent' — but it never warns that delete is irreversible or that the destructive operations need prior approval, which is left entirely to the schema's confirm field.

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 tight sentences with the action inventory front-loaded and the useful 'No email is sent' reassurance early. Minor inefficiency: the action list is incomplete relative to the schema's oneOf branches, and the settings prerequisite sentence is contextless on its own.

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 multi-action, destructive, no-output-schema tool, an agent still lacks the workflow ordering (create returns DNS records that must be applied before verify), a description of the 'check' action, and any statement about delete irreversibility. What is present is accurate but not sufficient to drive the whole lifecycle confidently.

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%, so parameters (domain object, domain_id, wildcard, subdomain, confirm) are already documented in the schema. The description adds no format, constraint, or relationship detail beyond the schema, so baseline 3 applies.

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 names specific verbs and a concrete resource ('Create/update a sending domain', 'verify DNS records', 'delete a custom domain'), which separates it from siblings like spur_manage_email_sender and spur_manage_return_address. It does not mention the 'check' action that the schema supports, so the stated scope is slightly narrower than the actual tool.

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?

Usage is implied by the domain-setup context, and it gives one prerequisite ('If credentials are required, complete that step in Spur settings'), but it never states when to choose this over adjacent tools or what the create-then-verify ordering should be.

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