Skip to main content
Glama

Prices by ending

ending_prices
Read-onlyIdempotent

The public list price of registering a domain on each ending, in USD: first year, renewal, fewest years sold for, and an on_offer flag. Leave endings out for every priced ending, cheapest first.

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

Input Schema

NameRequiredDescriptionDefault
endingsNoOptional endings, such as ["io", "ai", "dev"]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds real context beyond that: currency (USD), the exact set of returned fields, the on_offer flag, and the default ordering ('cheapest first') when no endings are supplied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, both dense with information: the first enumerates return fields, the second states the default-scope behavior. No filler, and the key content is front-loaded.

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 no output schema and a single optional parameter, the description carries the return-value burden and does so by naming each field and the ordering. The phrasing 'fewest years sold for' is slightly opaque and no pagination or result-size limits are mentioned, but nothing critical to invoking it correctly 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 the baseline is 3, but the description adds meaning the schema does not: omitting `endings` returns every priced ending, and results come back ordered cheapest first. The optionality and example format are already in the schema, so the added value is modest rather than exhaustive.

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?

The description states exactly what is returned: list prices per domain ending in USD, with named fields (first year, renewal, fewest years sold, on_offer). It is unambiguous and clearly distinct from the sibling tools (check_domains, search_name, domain_details), though it phrases the purpose as a resource listing rather than an explicit verb.

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: the tool is obviously a price-lookup, and 'Leave endings out for every priced ending' tells the agent how to broaden the query. There is no explicit statement of when to call this versus check_domains or domain_details, and no exclusions or prerequisites.

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