Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Industry events of one month

ud_list_events
Read-onlyIdempotent

The industry events of one month, in date order, then the events still without a date. 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 observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the safety profile is covered. The description adds a genuinely non-obvious behavioral fact: results are sorted by date with undated events appended at the end, which affects how the agent should interpret ordering.

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?

Two short sentences with zero filler, and the most decision-relevant fact (month scoping plus sort order) is front-loaded. Nothing is repeated from the schema descriptions.

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 and full annotation and parameter coverage, the description only needs to add scoping and ordering, which it does. What remains missing is any routing signal relative to the agenda and single-event siblings.

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%, so month bounds, the field whitelist, the country filter scope and the category enum are all already documented in the schema. The description adds nothing parameter-specific beyond restating optionality, which matches the baseline 3 for a fully documented 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 names the resource precisely (industry events of one month) and adds the ordering rule, so an agent knows this is a month-scoped listing rather than a per-entity lookup like ud_get_event. It never explicitly contrasts itself with siblings such as ud_get_agenda, so it stops short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

"Every input is optional" hints that a zero-argument call is valid and returns the current month, but there is no statement of when to prefer this over ud_get_event or ud_get_agenda, and no exclusion conditions. The agent must infer routing from the sibling names alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Unique Domains toolsInspect
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.

Resources