Skip to main content
Glama
vishalsg42

munim

by vishalsg42
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

plan_mail_setup

Plans email setup for a client domain, returning a plan_id and a list of DNS records to create or replace. It changes no client DNS, so you can review proposed changes before applying them.

Instructions

Work out what setting up email for this client's domain would change.

Returns a plan_id and every record that would be created or replaced, each with its current published value beside the proposed one, and a count of how many need a person to approve them. Touches no client DNS.

One honest note: planning creates the sending domain in your own Resend account, because Resend publishes no DKIM values until the domain exists. Pass the plan_id to apply_mail_setup to carry it out, or use fix, which plans and applies in one call and stops for approval in between.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
clientYesThe client to act on, by the name you registered them under. A write resolves this one client's credentials and no other.
domainYesThe domain to send mail from, for example acme.example. Uses the client's registered domain when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.5.0
    • addedInput schema / properties / client / description
      Added value: +"The client to act on, by the name you registered them under. A write resolves this one client's credentials and no other."
    • addedInput schema / properties / domain / description
      Added value: +"The domain to send mail from, for example acme.example. Uses the client's registered domain when omitted."
  2. First observedv0.4.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and it does so thoroughly: it discloses a non-obvious side effect ('planning creates the sending domain in your own Resend account'), reassures that client DNS is untouched, and describes the return payload (plan_id, records with current/proposed values, approval count). No behavior is hidden or misrepresented.

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?

The description is five sentences, each adding essential information: purpose, output, safety, side-effect disclosure, and routing to alternatives. It is front-loaded with the main purpose and uses minimal words to convey a complex behavior.

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

Completeness5/5

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

For a planning tool with no output schema, the description fully covers what the agent needs: the output structure, the side effect, the safe nature, and how to proceed afterward. There are no critical gaps for correct invocation.

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?

The input schema provides 100% coverage with detailed descriptions for both parameters (client and domain), so the baseline is 3. The tool description adds no extra parameter-specific meaning beyond the schema, which is acceptable given the schema's quality.

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 verb ('work out') and a clear resource ('what setting up email for this client's domain would change'), and immediately distinguishes itself from siblings by naming apply_mail_setup and fix. It leaves no ambiguity about the tool's function.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly tells the agent when to use this tool versus alternatives: 'Pass the plan_id to apply_mail_setup to carry it out, or use fix, which plans and applies in one call and stops for approval in between.' It also notes the safe nature ('Touches no client DNS') which guides risk-aware usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools