Skip to main content
Glama

EPP Status Code Reference

epp_status
Read-onlyIdempotent

Explain domain EPP status codes: what a code means, why it is set, how serious it is, and what the holder can do. Matches on the code, its aliases, or a category name; call with no query to list every code. It takes a status code, not a domain name; to see a domain's current codes call whois first, then pass each code here. Use this to interpret the status field returned by whois instead of relying on recall.

Related: whois, expired, monitor.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "epp_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoStatus code, alias, or category (e.g. 'clientHold', 'redemption period', 'Grace Period'). Omit to list every code

Output Schema

NameRequiredDescriptionDefault
dataNoMatching status codes
errorNo
totalNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world, non-destructive behavior, so the description's burden is lower. It adds useful matching semantics (code, alias, or category name) and the empty-query listing behavior that annotations do not express; it does not restate safety traits, which is correct.

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?

Four front-loaded sentences with the purpose, matching rules, prerequisite, and rationale each earning their place. The trailing 'Related: whois, expired, monitor' is mildly redundant since whois was already covered and the expired/monitor relationships are left unspecified.

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?

A single optional parameter tool with a full output schema and complete annotations needs exactly this much: what it returns conceptually, how to invoke it with or without a query, and what must precede it. Nothing required for correct invocation is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3, but the description adds meaning the schema does not: the query is a code/alias/category and specifically not a domain name, and omitting it triggers a full listing. That typo-proofing of the parameter's type goes beyond the schema's example text.

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?

Names a specific verb and resource ('Explain domain EPP status codes') and enumerates what the explanation covers: meaning, why set, severity, and holder remediation. It explicitly distinguishes itself from whois, so an agent knows this is a reference lookup rather than a domain-query tool.

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 call sequence ('call whois first, then pass each code here'), a zero-argument mode ('call with no query to list every code'), and a stated negative ('takes a status code, not a domain name'). It also says why to use it instead of memory, leaving no ambiguity about when to reach for it.

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.