Skip to main content
Glama

TLD Pricing

price
Read-onlyIdempotent

Return standard registration and renewal price for a TLD.

Related: 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": {
      "tld": "<tld>"
    },
    "name": "price"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldYesTLD to query, comma-separated for multiple (e.g., 'com', 'com,io,ai')

Output Schema

NameRequiredDescriptionDefault
dataNo
errorNo
totalNoNumber of TLDs returned
successNo

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds only that the figures are 'standard registration and renewal' prices, leaving open the currency, whether premium tiers are excluded, and whether stale/cached data is possible. Modest added value over 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?

Two short sentences with the core purpose front-loaded and no filler. The trailing 'Related: available.' is cryptic enough that it costs a line without earning it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 values need no explanation, and one parameter is fully documented. Still missing is what 'standard' excludes (premium, aftermarket) and how this differs from market_price, which matters given the dense sibling set of pricing-adjacent tools.

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 single tld parameter is fully documented in-schema, including the comma-separated multi-TLD syntax, so the description adds no parameter meaning. The description's singular 'for a TLD' is slightly narrower than the schema's list support but not contradictory.

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-plus-resource: 'Return standard registration and renewal price for a TLD.' An agent can tell it returns pricing, though the qualifier 'standard' versus a market/premium price is not contrasted with the sibling market_price tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Related: available.' is a bare pointer with no described relationship and no when-to-use versus market_price, tld_check, or bulk_tld. The agent must infer that this is the per-TLD list-price lookup and that market_price covers aftermarket pricing.

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.