Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

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

ud_list_trends
Read-onlyIdempotent

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. Changed1 schema field changed
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +20
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description contributes the pagination model ('answers one page at a time'), which is genuinely behavioral, but that is largely mirrored by the `cursor` schema field. No mention of rate limits, auth needs, or ordering defaults beyond 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?

Three short sentences, purpose front-loaded, with the optionality note placed after the scenario. The opening sentence duplicates the title verbatim, which is mild waste but structurally sound.

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 100% parameter coverage, the description need not explain return values, and it correctly covers optionality and paging. Adequate for a read-only, fully-optional list tool, though it could note the default `sort=slug` behavior for an agent deciding page ordering.

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's meaning is already documented structurally; the description only restates that 'every input is optional' and that `limit` sets page size. No additional semantics (e.g., how `since` interacts with `sort=day`, or how `fields` trimming affects output) are added.

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 ('Every published trend') and what comes back with each one (latest edition figures, first and last edition day), so an agent can tell it apart from ud_get_trend. It stops short of explicitly contrasting itself with the single-trend or category-list siblings.

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?

It offers one motivating scenario ('when someone looks for rising topics to name a project after') but gives no when-not guidance and never names ud_get_trend or ud_list_trend_categories as alternatives. The `category` param pointing at `GET /trends/categories` implies the sibling relationship rather than stating it.

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