Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

One industry event with its organizer

ud_get_event
Read-onlyIdempotent

Retrieve details for a single industry event by slug, including organizer, location, dates, category, and description.

Instructions

One industry event with its organizer, location and description. Use it when someone asks for the details of one event. Pass slug (such as registrar-day-afnic-2027).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "ud_get_event"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesThe event's slug, at most 160 characters.
fieldsNoComma-separated top-level keys to keep: id, slug, title, startsOn, endsOn, category, countryCode, city, lat, lng, organizer, location, description.

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.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only that the response bundles organizer, location and description. It says nothing about what happens on an unknown slug (error vs. empty) or about the sparse-fieldset behavior of the fields parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the payload stated first, the triggering condition second and the parameter guidance last. Nothing is redundant and nothing needs trimming.

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, full annotation coverage and 100% schema coverage, the description only needs to state scope, when to use it and how to identify the record, which it does. It could go one step further by noting that slug must match an existing event and that fields narrows the payload.

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 documents both slug and fields, setting the baseline at 3. The concrete example 'registrar-day-afnic-2027' gives the agent a usable slug format that the schema's 'at most 160 characters' does not convey, but the fields projection parameter is never mentioned in the prose.

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 identifies a specific resource ('one industry event') and enumerates the payload contents (organizer, location, description), which implicitly contrasts with the plural sibling ud_list_events. It never uses a verb like 'fetch' or 'retrieve', but the resource and cardinality are unambiguous.

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 for the details of one event' gives a clear triggering context. It stops short of naming ud_list_events as the alternative for browsing or searching, so the when-not clause is absent.

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