Skip to main content
Glama

Cross-TLD Registration Check

tld_check
Read-onlyIdempotent

Check how a prefix is registered across core TLDs, returning per-TLD status and aggregate counts.

Related: bulk_tld, available.

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": {
      "prefix": "<prefix>"
    },
    "name": "tld_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
prefixYesKeyword without extension (e.g., 'openai')

Output Schema

NameRequiredDescriptionDefault
tldsNoStatus of core TLDs (com, net, org, io, ai, de). Values: registered, for_sale, expiring, or might_available
countNoTotal number of TLDs with this prefix registered
errorNoError message when success is false
prefixNo
successNo
gtlds_countNoNumber of gTLDs with this prefix registered
cctlds_countNoNumber of ccTLDs with this prefix registered

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered. The description contributes the return shape (per-TLD status plus aggregate counts) but nothing about rate limits, caching, quotas, or which TLD set is covered.

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?

One core sentence front-loads the action and the returned data, with a short related-links line after it. Nothing is padded, though the sibling line is a bare pointer rather than actionable guidance.

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?

With an output schema, rich annotations, and a single fully documented parameter, the description supplies enough to invoke the tool correctly. The only real gap is not knowing the actual TLD list being checked, which mildly affects interpreting the aggregate counts.

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% and the schema already spells out the 'keyword without extension' convention with an 'openai' example. The description adds no further meaning beyond confirming the input is a prefix, so the baseline applies.

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 ('Check') and resource ('registration across core TLDs') and says what comes back (per-TLD status and aggregate counts). It does not pin down which TLDs count as 'core' or differentiate itself from the named siblings, so it stops short of a 5.

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 'Related: bulk_tld, available' line points at alternatives but never states when to choose this tool versus them. Usage is only implied by the purpose sentence, leaving the agent to infer the selection rule.

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.