Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Names dropping on one day, counted by ending

ud_get_domain_drops
Read-onlyIdempotent

Query daily domain name drops by ending to learn how many names drop on a given UTC day, with optional pagination for results.

Instructions

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

NameRequiredDescriptionDefault
dayNoThe drop day, UTC; default today.
limitNoPage size, 20 at most.
cursorNoThe `meta.cursor` of the previous page.
fieldsNoComma-separated top-level keys to keep: count, byEnding, sample, id, name, ending, dropsOn, status.

Output Schema

NameRequiredDescriptionDefault
dataNo
metaNoThe day of the answer, and the page cursor of a list.
linksNoLinks of the answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A3.6/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 fully covered structurally. The description adds only that every input is optional and that limit controls page size — useful but thin, and it says nothing about ordering, how pagination terminates, or what the grouping guarantees. With annotations and a full output schema carrying most of the weight, a 3 is appropriate.

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?

Three short sentences, front-loaded with the purpose before the usage cue, and nothing padded. The only slight waste is echoing 'counted by ending' from the title and repeating the page-size fact that the schema already states.

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 read-only, four-optional-parameter aggregation tool with a full output schema, the description covers purpose, trigger condition and pagination entry point adequately. The remaining gap is minor: nothing tells the agent how to continue paging or what the cursor-absent state means, but the schema's cursor description largely compensates.

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 day, limit, cursor and fields are all documented in the schema itself, including the UTC default and the 20-item cap. The description's note that all inputs are optional and that limit is the page size restates the schema rather than adding new meaning such as cursor semantics or field-selection behavior. Baseline 3 holds.

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?

Names a specific verb-and-resource combination — counting names that drop on a single day, broken out by ending — which is precise enough that an agent can distinguish it from aggregate tools like ud_get_tld_stats or per-name lookups like ud_get_name. It stops short of naming any sibling explicitly, so the differentiation relies on the resource noun rather than an outright contrast.

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?

The second sentence gives a concrete triggering condition: 'when someone asks how many names drop on a given day, and on which endings,' which maps a user question shape to this tool. There is no exclusion clause or mention of alternatives (for example, per-name drop details), so an agent must infer the boundary itself.

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

Deploy Server

Other Tools