Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Every published trend with its latest edition figures and its first and last edition day

ud_list_trends
Read-onlyIdempotent

Lists published trends page by page with edition figures and first/last edition dates, filterable by category, lane, and date, to help find rising topics for project names.

Instructions

Every published trend with its latest edition figures and its first and last edition day. Use it when someone looks for rising topics to name a project after; it answers one page at a time. Every input is optional; limit sets the page size.

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

Input Schema

NameRequiredDescriptionDefault
laneNoThe editions' lane the trend was drawn from.
sortNo`slug`, or `day` for the last edition day, newest first.slug
limitNoPage size, 20 at most.
sinceNoTrends whose last edition day is on or after this UTC day.
cursorNoThe `meta.cursor` of the previous page.
fieldsNoComma-separated top-level keys to keep: slug, name, category, definition, volume, growth, lane, headWord, whyNow, firstEditionOn, lastEditionOn, editionCount.
categoryNoA category slug (`GET /trends/categories`).

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

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

Annotations already declare read-only, idempotent, non-destructive, closed-world behavior, so the safety bar is largely met. The description adds that the tool "answers one page at a time" and that all inputs are optional, which is genuine pagination context beyond the annotations, but it says nothing about default result size beyond the `limit` hint or about ordering behavior.

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 scope statement and the paging caveat before the parameter note. No filler; the slightly quirky "name a project after" phrasing costs little but is less precise than a stated filtering criterion would be.

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 output schema, rich annotations, and complete schema coverage on seven optional parameters, the description only needs to convey scope and paging, which it does. Missing is any statement of default ordering behavior or how the cursor round-trips, minor given the schema already describes `cursor` as `meta.cursor` of the previous page.

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 every parameter including the enum values for `lane` and `sort`, `since`, and `cursor` is already documented in the schema. The description's only parameter remark ("Every input is optional; `limit` sets the page size") restates the schema rather than extending it. Baseline 3 is appropriate.

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?

Names a specific resource and scope: "Every published trend with its latest edition figures and its first and last edition day," which clearly distinguishes a bulk trend listing from single-trend or category siblings. The opening is a noun phrase rather than a verb, but the resource and payload 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 Guidelines3/5

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

Gives one narrow usage scenario ("when someone looks for rising topics to name a project after") but no when-not conditions and no named alternatives such as the single-trend getter or the categories lister. An agent must infer from sibling names which tool handles filtering by category versus fetching one trend.

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