Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Catalog headline totals for the latest day

ud_get_catalog_stats
Read-onlyIdempotent

Retrieve catalog headline totals for the latest day to answer how many domain names the catalog tracks and how many are open.

Instructions

Catalog headline totals for the latest day. Use it when someone asks how many names the catalog tracks and how many are open. Takes no input.

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_catalog_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: day, domains, words, tlds.

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

B3.4/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 safety is covered. The description adds useful scope ('latest day', i.e. recency of the snapshot) but then claims 'Takes no input', which is inaccurate given the schema's optional fields projection parameter — mildly misleading rather than contradicting 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?

Three short sentences, front-loaded with the resource and followed by the usage trigger — no padding. The final sentence 'Takes no input' is not just wasted but incorrect, which is the only structural flaw.

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 value explanation is not required, and the description does convey the two headline figures and the latest-day scope. However, for a tool with one optional projection parameter, omitting and effectively denying that parameter leaves the agent unable to shape the response.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% so the baseline would be 3, but the description actively works against the schema by asserting that the tool takes no input, leaving the optional 'fields' projection (day, domains, words, tlds) entirely unexplained and implicitly denied. That is misinformation about the only parameter rather than neutral omission.

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 resource and scope: headline totals for the latest day, plus the concrete questions it answers (how many names are tracked, how many are open). It does not explicitly distinguish itself from aggregation siblings such as ud_get_tld_stats, but the 'headline/whole-catalog' framing is specific enough to route correctly.

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?

"Use it when someone asks how many names the catalog tracks and how many are open" gives an explicit trigger condition tied to user intent. It stops short of naming alternatives or exclusions (e.g. when to prefer ud_get_tld_stats for per-TLD breakdowns), so it is clear context without routing rules.

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