Skip to main content
Glama

get_transfer_auth_code

Read-only

Return the EPP transfer auth code for a domain owned by the authenticated customer. The secret is fetched only on demand.

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": "get_transfer_auth_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly and non-destructive, but the description adds real value: the ownership/authentication constraint on which domains qualify, and the on-demand, non-caching nature of the secret retrieval, which signals its sensitivity. It does not describe error behavior when the domain is not owned or not transfer-eligible.

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?

Two short sentences, with the action and scope front-loaded, and the sensitivity note placed second. Nothing is redundant or wasted.

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 return-value documentation is not required, and the description covers the purpose, the ownership prerequisite, and retrieval semantics. It omits failure and eligibility conditions, which matter for a secret-returning tool, but those are secondary.

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 a single required parameter, domain, with 0% schema description coverage. The description clarifies that the domain must belong to the authenticated customer, which compensates partially, but it gives no format detail such as whether the input is a unicode or punycode name, which would determine whether a call succeeds.

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?

States a specific verb and resource: returns the EPP transfer auth code for a domain. It also scopes it to domains 'owned by the authenticated customer.' It does not name the sibling regenerate_transfer_auth_code or explain how fetching differs from regenerating, which is the most likely point of confusion.

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?

'The secret is fetched only on demand' implies this is a non-destructive read as opposed to a rotation, but the guidance is only implied. No explicit when-to-use versus the sibling regenerate_transfer_auth_code, and no note on whether it fails when a transfer lock or transfer-pending state applies.

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.