Unique Domains

Whole public agenda of one month

ud_get_agenda

Read-onlyIdempotent

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

Name	Required	Description
`tld`	No	A bare root ending the catalog knows.
`month`	No	`YYYY-MM`, from the month of today minus 30 days to today plus 18 months; the current month by default.
`fields`	No	Comma-separated top-level keys to keep: entries, recentlyAdded, undated.
`country`	No	ISO 3166-1 alpha-2; filters events only.
`category`	No	An event category, or `launches` for the TLD entries.

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
- removedOutput schema / properties / data / properties / entries / items / properties / id
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / data / properties / recentlyAdded / items / properties / id
```
Removed value: -{
-  "type": "string"
-}
```
- removedOutput schema / properties / data / properties / undated / items / properties / id
```
Removed value: -{
-  "type": "string"
-}
```
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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only that every input is optional, which the schema already shows, and says nothing about result shape or ordering beyond the content list.

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 definition before the usage trigger. The content list is repeated in sentence two, a minor redundancy, but nothing is padded.

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 an output schema present, full parameter documentation and rich annotations, the description only needs to convey scope and trigger, which it does. A note on how the month window interacts with the default 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%, including the month range and the launches category value, so the schema carries parameter meaning. The description's only parameter remark ('Every input is optional') duplicates the zero-required-parameters fact rather than adding semantics.

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: the whole public agenda of one month, enumerating its contents (industry events, TLD launch phases, registry changes). This distinguishes it from a plain event list, though it never names a sibling to contrast with.

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?

Gives an explicit trigger: 'Use it when someone asks what happens in a month.' It restates the covered content types, which helps routing, but offers no when-not guidance or named alternative for narrower queries.

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.