Unique Domains

Names dropping on one day, counted by ending

ud_get_domain_drops

Read-onlyIdempotent

The names dropping on one day, counted by ending. Use it when someone asks how many names drop on a given day, and on which endings. Every input is optional; limit sets the page size.

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

Input Schema

Name	Required	Description
`day`	No	The drop day, UTC; default today.
`limit`	No	Page size, 20 at most.
`cursor`	No	The `meta.cursor` of the previous page.
`fields`	No	Comma-separated top-level keys to keep: count, byEnding, sample, name, ending, dropsOn, status.

Output Schema

Name	Required	Description
`data`	No
`meta`	No	The day of the answer, and the page cursor of a list.
`links`	No	Links of the answer.

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedNov 11, 2026

changedInput schema / properties / fields / description

Previous value: -"Comma-separated top-level keys to keep: count, byEnding, sample, id, name, ending, dropsOn, status."New value: +"Comma-separated top-level keys to keep: count, byEnding, sample, name, ending, dropsOn, status."

changedInput schema / properties / limit / maximum
```
Previous value: -100New value: +20
```

changedOutput schema / properties / data / anyOf

Previous value: -[
-  {
-    "properties": {
-      "byEnding": {
-        "items": {
-          "properties": {
-            "count": {
-              "type": "integer"
-            },
-            "ending": {
-              "type": "string"
-            }
-          },
-          "type": "object"
-        },
-        "type": "array"
-      },
-      "count": {
-        "type": "integer"
-      },
-      "sample": {
-        "items": {
-          "properties": {
-            "dropsOn": {
-              "type": "string"
-            },
-            "ending": {
-              "type": "string"
-            }
-          },
-          "type": "object"
-        },
-        "type": "array"
-      }
-    },
-    "type": "object"
-  },
-  {
-    "items": {
-      "properties": {
-        "dropsOn": {
-          "type": "string"
-        },
-        "ending": {
-          "type": "string"
-        },
-        "id": {
-          "type": "string"
-        },
-        "name": {
-          "type": "string"
-        },
-        "status": {
-          "type": "string"
-        }
-      },
-      "type": "object"
-    },
-    "type": "array"
-  }
-]New value: +[
+  {
+    "properties": {
+      "byEnding": {
+        "items": {
+          "properties": {
+            "count": {
+              "type": "integer"
+            },
+            "ending": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      },
+      "count": {
+        "type": "integer"
+      },
+      "sample": {
+        "items": {
+          "properties": {
+            "dropsOn": {
+              "type": "string"
+            },
+            "ending": {
+              "type": "string"
+            }
+          },
+          "type": "object"
+        },
+        "type": "array"
+      }
+    },
+    "type": "object"
+  },
+  {
+    "items": {
+      "properties": {
+        "dropsOn": {
+          "type": "string"
+        },
+        "ending": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        },
+        "status": {
+          "type": "string"
+        }
+      },
+      "type": "object"
+    },
+    "type": "array"
+  }
+]

First observedNov 9, 2026

TDQS

A3.6/5.0

Behavior3/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 that all inputs are optional and that limit controls page size, but says nothing about pagination behavior via cursor or what the counting granularity is beyond the title.

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, front-loaded with the purpose and followed by the trigger condition. The first sentence is essentially a restatement of the title, which is mild redundancy but not disruptive.

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?

For a low-complexity read-only aggregate with a full output schema and fully documented parameters, the description covers purpose, trigger and pagination hint. Nothing critical is missing, though a note on how cursor paging interacts with limit would round it out.

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%, so the schema already documents day, limit, cursor and fields thoroughly. The description only reiterates optionality and limit's role as page size, adding little meaning beyond the schema (e.g. no guidance on choosing values for fields or cursor usage).

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 names the resource (domain name drops) and the aggregation axis (one day, counted by ending), which is enough to distinguish it from broad list tools like ud_list_domains. It is a noun phrase rather than a verb+object, but the scope is unambiguous.

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 triggering question: 'when someone asks how many names drop on a given day, and on which endings.' No when-not conditions or named alternatives (e.g. ud_get_word_endings for cross-day ending trends), so it falls short of a 5.

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

All Unique Domains 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.