Skip to main content
Glama

Get my domain transfers

get_my_domain_transfers
Read-onlyIdempotent

Where the customer's inbound domain transfers stand, one row per domain, with counts: awaiting_code (paid, the customer still has to enter the transfer code in their dashboard — or, for a .uk domain (method ips_tag), confirm there that the current registrar changed the IPS tag to NAMESILO), queued (code in, being submitted), refused (the registrar rejected it — the reason says what to fix before entering the code again), needs_attention (we are checking it with the registrar), pending_registry (submitted, usually done in about 5 days), completed, cancelled. Pass cartId to see one checkout's batch. Use after prepare_domain_transfers, or when they ask "did my transfers go through?". Codes are entered in the dashboard, never here. Read-only.

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

Input Schema

NameRequiredDescriptionDefault
cartIdNoOptional: the cartId prepare_domain_transfers returned, to see only that batch.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / cartId / description
      Previous value: -"Optional: the cartId Prepare domain transfers (needs a read-write connection) returned, to see only that batch."New value: +"Optional: the cartId prepare_domain_transfers returned, to see only that batch."
  2. Changed1 schema field changed
    • changedInput schema / properties / cartId / description
      Previous value: -"Optional: the cartId prepare_domain_transfers returned, to see only that batch."New value: +"Optional: the cartId Prepare domain transfers (needs a read-write connection) returned, to see only that batch."
  3. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds substantive behavior: what each status means operationally, that refused includes a reason to fix before retrying, and that pending_registry typically completes in ~5 days. That timing and remediation context is not derivable from the annotations.

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 answer (where transfers stand, one row per domain) and every status gloss earns its place. The status list is delivered as one very long run-on sentence with nested asides, which hurts scannability slightly.

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?

With no output schema, the description carries the burden of describing the return shape and does so: one row per domain, status vocabulary, counts, and per-status remediation meaning. For a no-required-param read tool this is enough to call and interpret correctly.

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?

Schema coverage is 100%, so the single optional cartId is already documented in the schema, including that prepare_domain_transfers returns it. The description's 'Pass cartId to see one checkout's batch' restates rather than extends that meaning, so the baseline 3 applies.

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 resource (the customer's inbound domain transfers) with the exact shape returned — one row per domain plus status counts — and enumerates every status. It is clearly distinguishable from list_my_domains or get_migration_status, so an agent knows exactly which tool to reach for.

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 explicit when-to-use triggers ('Use after prepare_domain_transfers, or when they ask "did my transfers go through?"'), an explicit exclusion ('Codes are entered in the dashboard, never here'), and a scoping rule for cartId. Nothing about routing is left to inference.

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