Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Industry events of one month

ud_list_events
Read-onlyIdempotent

List domain and internet industry events for a chosen month in date order, with undated events last, and filter by country or category to find relevant agenda items.

Instructions

The industry events of one month, in date order, then the events still without a date. Use it when someone asks about domain or internet industry events in a month. 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_list_events"
  }
}

Input Schema

NameRequiredDescriptionDefault
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: id, slug, kind, title, startsOn, endsOn, category, countryCode, city, lat, lng.
countryNoISO 3166-1 alpha-2; filters events only.
categoryNoAn event category.

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

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the annotations, the description adds useful behavioral detail about result ordering: dated events first, then events still without a date. It also notes that every input is optional, though that largely repeats the schema.

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?

The definition is short and front-loads the scope and ordering. There is minor redundancy in repeating the month context and stating that all inputs are optional, but it remains efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only list tool with a full input schema, rich annotations, and an output schema, the description is complete enough. It covers purpose, usage context, and result ordering without needing to restate schema details.

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 coverage is 100%, so the schema already explains month, fields, country, and category thoroughly. The description adds little parameter meaning beyond saying all inputs are optional, which is already evident from 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 clearly states the resource and scope: industry events for one month, including ordering by date and then undated events. It does not explicitly name a sibling alternative such as ud_get_event, so it is clear but lacks explicit sibling differentiation.

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 a direct usage cue: use when someone asks about domain or internet industry events in a month. It does not state when not to use it or name alternatives, but the context is clear.

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