Skip to main content
Glama

Check DNS provider approval

domainAuthorizationStatus
Read-onlyIdempotent

Ask whether the human has approved a one-click DNS authorization yet, and read status (pending, authorized, failed or revoked) plus the plain-language message. Approval remains pending while the human has not completed the provider flow. It never returns a link or a credential; this tool does not start or replace an authorization request and does not verify DNS records. authorized records the completed approval; failed includes the failure message.

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>",
      "domainId": "<domainId>"
    },
    "name": "domainAuthorizationStatus"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainIdYes
projectIdYes

Output Schema

NameRequiredDescriptionDefault
authorizationYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive, closed-world, so the bar is lower; the description still adds real value by explaining that approval stays 'pending' until the human finishes the provider flow, that no link or credential is ever returned, and that 'failed' carries the failure message. It does not discuss polling cadence or whether pending is terminal.

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?

Front-loaded with the core action and the status vocabulary, and every sentence carries information. The pending condition is stated twice ('remains pending while the human has not completed the provider flow' and 'authorized records the completed approval'), a small redundancy.

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

Completeness4/5

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

An output schema exists, so the description need not explain the shape of status/message, and it sensibly focuses on state semantics and safety boundaries instead. The only real gap is the complete absence of parameter meaning for a two-required-param tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for both required parameters (projectId, domainId), and the description says nothing about what either identifies or how they are obtained. The UUID formats are conveyed by the schema patterns only; the description contributes no meaning beyond the parameter names.

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 states a specific verb and resource ('ask whether the human has approved a one-click DNS authorization... and read status'), enumerates the four status values, and rules out what the tool is not (it does not start or replace an authorization request, does not verify DNS records). That behaviorally separates it from domainAuthorize/domainVerify, though no sibling is named explicitly.

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

Usage Guidelines4/5

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

Usage is clearly implied as polling the state of an in-flight human approval flow, and negative guidance is explicit: it is not the tool that starts or replaces a request, and it is not the tool that verifies DNS records. It stops short of naming the alternative tools to call for those actions.

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