Skip to main content
Glama

Get domain auth code

get_authcode
Read-only

Get the auth code (transfer key) for a domain. Whoever holds it can move the domain away, and it then sits in this conversation.

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": {
      "id": "<id>"
    },
    "name": "get_authcode"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe domain ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, which undersells that this read exposes a credential. The description supplies that context: the holder can transfer the domain away, and the code is retained in the conversation, which is a meaningful disclosure about secret persistence in the transcript. It doesn't say whether the code expires, is one-time, or whether the call is rate-limited.

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?

Two short sentences, purpose front-loaded and risk immediately after. The closing clause 'it then sits in this conversation' is a little colloquial but carries real information, so little is 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?

For a single-parameter read tool with no output schema, the description covers what is retrieved and the consequence of holding it. Preconditions for a successful retrieval (e.g. transfer lock state) and whether the value is cached or regenerated are the main omissions.

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

Parameters5/5

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

With one required parameter and 100% schema description coverage (including a 24-hex-character pattern), the schema carries all parameter meaning; the description correctly adds nothing redundant. No parameter semantics are at risk of being lost.

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 ('Get the auth code') and parenthetically defines what that resource is ('transfer key'), which separates it from the plain domain-detail retrieval implied by get_domain. It stops short of explicitly naming a sibling, but the object is unambiguous.

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 only implied by the mechanics described: you'd call this when preparing to move a domain away. There is no statement of preconditions such as ownership, an unlocked transfer lock, or which follow-up tool consumes the code.

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.