Skip to main content
Glama
agentisend

agentisend

Hand DNS setup to a person

domains_setup_link

Generates a shareable, no-login URL so the domain owner can publish DNS records themselves when you cannot, valid for 7 days and replaced by later calls.

Instructions

Purpose: a page the person who owns DNS can open without signing in. Call this when you cannot publish the records yourself, and send them the url. NOT for: reading the records yourself (setup_domain) or checking them (verify_domain). Returns: url and expires_at. The link lasts 7 days. A later call replaces it; the previous url stops opening. Pass the domain id or the domain name as domain. name means the same thing.

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": {
      "domain": "<domain>"
    },
    "name": "domains_setup_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain id from create_domain, or the domain name. name is an alias for this argument.
idempotency_keyNoYour own key for this action. Retrying with the same key returns the first result instead of doing it twice — send one whenever a retry could double the effect.

Output Schema

NameRequiredDescriptionDefault
urlNoA page the person who owns DNS can open. No sign-in.
errorNoPresent instead of the fields above when the call was refused: code, message, fix, docs_url, retryable and, when waiting helps, retry_after_seconds.
expires_atNoWhen the link stops opening.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Goes well beyond the annotations, which only say it is a non-read-only, non-idempotent, non-destructive write. The description discloses the 7-day lifetime, that a later call invalidates the previous url, and what is returned (url and expires_at) — exactly the lifecycle facts an agent needs before issuing a shareable credential.

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?

Labelled Purpose / NOT for / Returns blocks with zero filler, and the trigger condition is front-loaded. The final sentence about the domain/name alias is the only near-redundant line.

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 two-parameter tool with an output schema, the description supplies the missing pieces: when to choose it, what to do with the result, and how long the link lives plus how replacement works. Nothing material is left for the agent to infer.

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 coverage is 100% and the schema already documents that domain accepts an id or the name and that name is an alias, so the closing sentence largely restates structured data. It adds no new format or constraint guidance, which is a baseline 3 when the schema does the work.

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?

States a specific outcome: a signed-out page for the DNS owner that you send as a url. It immediately distinguishes itself from setup_domain (reading the records) and verify_domain (checking them), so an agent can pick it without opening any schema.

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?

Gives an explicit trigger ('call this when you cannot publish the records yourself') and explicit exclusions naming the two sibling tools that cover the cases this tool does not. The action to take after calling ('send them the url') is also stated.

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