Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Whole public agenda of one month

ud_get_agenda
Read-onlyIdempotent

Retrieve the public agenda for a given month, including industry events, TLD launch phases, and registry changes, with optional filters for TLD, country, category, and fields.

Instructions

The whole public agenda of one month: industry events, TLD launch phases and registry changes. Use it when someone asks what happens in a month: events, ending launches and registry changes. Every input is optional.

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

Input Schema

NameRequiredDescriptionDefault
tldNoA bare root ending the catalog knows.
monthNo`YYYY-MM`, from the month of today minus 30 days to today plus 18 months; the current month by default.
fieldsNoComma-separated top-level keys to keep: entries, recentlyAdded, undated.
countryNoISO 3166-1 alpha-2; filters events only.
categoryNoAn event category, or `launches` for the TLD entries.

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 this a read-only, idempotent, closed-world, non-destructive operation, so the safety profile is fully covered. The description adds the useful fact that every input is optional (the call works with zero arguments), but says nothing about result size, pagination, or default scoping beyond what the schema already states.

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 contents, with no filler. The third sentence's list of contents largely repeats the first sentence's list, which is a minor redundancy but it reinforces the use case rather than obscuring it.

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 a full parameter schema, a complete annotation set, and an output schema that documents return shape, the description only needs to convey purpose and when to call it — both are present. The remaining gap is that it doesn't note how the aggregate relates to the narrower event/TLD tools, which matters for a five-parameter aggregator in a large tool family.

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 the month range and the country/category scoping, so the schema does the heavy lifting and baseline 3 applies. The description only restates that all inputs are optional and hints at the event-versus-launch split, adding no format or precedence detail beyond the schema.

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 a concrete resource (the whole public agenda of one month) and enumerates its contents: industry events, TLD launch phases and registry changes. That is far more specific than the title alone, though it never explicitly contrasts itself with the sibling list/event tools (ud_list_events, ud_get_event), so sibling differentiation is inferred rather than stated.

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 what happens in a month: events, ending launches and registry changes" gives a clear triggering context for the agent. It stops short of exclusions or naming an alternative tool for narrower lookups, so it is clear context without routing guidance.

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