Skip to main content
Glama

Read sign-in email setup

appAuthEmailStatus
Read-onlyIdempotent

Read one owned app’s sign-in email setup, as its Email page shows it: its resolved sender, the email provider’s identity for the app’s own domain, and the DNS records, all under send.<domain>, each with relativeName, the name a zone editor takes. It writes nothing and asks the provider nothing but a read. The result’s state distinguishes the observations: configured means a live read of the app’s auth service returned the resolved sender; not_configured, it was read and carries another sender (or none), or Tofu cannot set one yet; disabled, this deployment sends no app mail (the app is unaffected and keeps sending its own mail); unavailable, the read produced NOTHING, which says nothing about the app. Nor does an email provider that was not reached (records is then empty). sender is resolved from what the provider really reported, never a sender that has not moved: a domain whose records were written but not yet observed is NOT connected.

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": {
      "projectId": "<projectId>"
    },
    "name": "appAuthEmailStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Output Schema

NameRequiredDescriptionDefault
dnsYes
stateYes
domainYes
senderYes
appNameYes
enabledYes
messageYes
recordsYes
siteUrlYes
identityYes
nextStepsYes
observedSenderYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the supplied annotations (readOnly/openWorld/idempotent/non-destructive) by disclosing that it writes nothing and performs only a provider read, and by carefully bounding failure semantics: `unavailable` means the read produced nothing and says nothing about the app, and an unreached provider yields empty `records`. It also warns that a sender is only reported once observed, so a written-but-unobserved domain is not connected.

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?

The core capability is front-loaded in the first clause, followed by return fields and state semantics in a logical order. It is dense and occasionally convoluted ('Nor does an email provider that was not reached'), but nearly every sentence carries real interpretive value.

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?

An output schema exists, so return values need not be re-explained, yet the description goes further by defining each `state` value and its evidentiary limits — exactly the ambiguity a status tool creates. For a single-parameter read tool, nothing an agent needs to call or interpret it is missing.

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?

There is one parameter (`projectId`) with 0% schema description coverage, and the description does not mention it at all. The schema does supply type, UUID format and pattern, and the parameter is a self-evident identifier, so the gap is tolerable but the description adds no meaning here.

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 verb and resource — reading one owned app's sign-in email setup — and enumerates exactly what is returned (resolved `sender`, provider `identity`, DNS `records` under `send.<domain>`). This clearly separates it from the sibling mutation tools appAuthEmailConnect and appAuthEmailDisconnect.

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 rather than stated: it is a read of current email setup, and the `state` vocabulary (`configured`, `not_configured`, `disabled`, `unavailable`) tells the agent how to interpret what it gets back. However, the description never explicitly says when to call this versus appAuthEmailConnect or appAuthEmailStatus, nor any prerequisites.

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