TLD Bench

Price history

price_history

Read-onlyIdempotent

Use this when the user asks how an extension's prices have moved or whether a rise is coming. Returns each registrar's price periods (changes only) and the registry's announced wholesale changes.

Input Schema

Name	Required	Description
`tld`	Yes	an extension: com, .io, co.uk or рф
`since`	No	YYYY-MM-DD: only periods that end on or after it
`currency`	No	ISO 4217 currency for prices (default USD); converted at the ECB's daily rate, disclosed in `fx`
`operation`	No	register (a new registration, year 1), renew (one more year), transfer (move in; usually adds a year), restore (redeem an expired domain in its redemption period)
`registrar`	No	one registrar's id

Output Schema

Name	Required	Description
`fx`	Yes	How converted prices were converted; null when nothing needed converting.
`tld`	Yes
`url`	Yes	the page on tldbench.com with the full comparison
`as_of`	Yes	when the newest price in this response was collected
`series`	Yes
`currency`	Yes	ISO 4217
`registry_events`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 6, 2026

addedOutput schema / properties / series / items / properties / registrar / properties / note

Added value: +{
+  "anyOf": [
+    {
+      "description": "A short, sourced note about the registrar's prices (not a price we rank by).",
+      "properties": {
+        "checked_on": {
+          "anyOf": [
+            {
+              "examples": [
+                "2026-11-05"
+              ],
+              "format": "date",
+              "type": "string"
+            },
+            {
+              "type": "null"
+            }
+          ]
+        },
+        "text": {
+          "examples": [
+            "NameSilo's free discount program prices .com at $12.00 (retail $19.99)."
+          ],
+          "type": "string"
+        },
+        "url": {
+          "description": "where the note's facts come from",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "text",
+        "url",
+        "checked_on"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}

addedOutput schema / properties / series / items / properties / registrar / properties / pricing_tier

Added value: +{
+  "description": "retail: anyone can buy at these prices; reseller: the prices are a reseller account's tier (eNom's Silver), left out of consumer rankings unless include_resellers=true",
+  "enum": [
+    "retail",
+    "reseller"
+  ],
+  "type": "string"
+}

First observedNov 6, 2026

TDQS

A4.2/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 still adds real behavioral value by disclosing that only change periods are returned (not a dense time series) and that forward-looking registry wholesale announcements are included, which no annotation conveys.

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 with zero waste: the triggering condition comes first, the return content second. Nothing is redundant with the title or schema.

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 five parameters, full schema coverage, an output schema, and complete annotations, the description only needs to convey purpose and return shape, which it does. The 'changes only' and announced-changes clauses are the key facts an agent needs to interpret results correctly; only minor gaps remain around how the two data sets are combined in the response.

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 description coverage is 100%, including tld examples, since date semantics, currency conversion via ECB rates with an fx disclosure, operation enum meanings, and registrar id. The description adds no parameter-level meaning beyond the schema, so the baseline of 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?

The description names a specific resource and scope: registrar price periods (changes only) plus announced registry wholesale changes for an extension. This is clearly distinguishable from sibling tools such as cheapest_registrar or compare_tld_prices, which deal with current prices rather than historical movement.

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

Usage Guidelines4/5

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

It gives an explicit trigger ('when the user asks how an extension's prices have moved or whether a rise is coming'), which is strong usage guidance. It stops short of naming alternatives for cases like current-price comparison, so it is clear context but not full when-not/alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All TLD Bench tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?