Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

One trend

ud_get_trend
Read-onlyIdempotent

Retrieve a single trend by slug to view its latest data, head words, growth, edition figures, and observations for market analysis.

Instructions

One trend: its latest row, its head words, its figures at every edition and its latest observations. Use it when someone asks about one trend: how it grew and its key words. Pass slug (such as ambient-lights).

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

Input Schema

NameRequiredDescriptionDefault
slugYesThe trend's slug.
fieldsNoComma-separated top-level keys to keep: slug, name, category, definition, volume, growth, lane, headWord, whyNow, firstEditionOn, lastEditionOn, editionCount, headWords, editions, observations.

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 readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds some scope context (data spans every edition plus latest observations), but it does not mention errors for unknown slugs or what 'latest' means relative to freshness.

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?

Two sentences, front-loaded with the resource and its contents, then the invocation hint and parameter example. Minor redundancy in 'One trend' opening followed by 'when someone asks about one trend', but nothing wasteful enough to trim.

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?

Output schema exists, so return values need not be explained, and the two-parameter schema is fully documented. Nothing an agent needs to make the call is missing, though a brief note on what a 'trend' entity represents would help an unfamiliar agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description adds a concrete example value for the required slug ('such as ambient-lights'), which is genuinely useful for formatting the call. The optional fields parameter is left to the schema, which documents it fully.

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 (one trend) and enumerates the content it returns: latest row, head words, figures per edition, latest observations. It is clearly distinguishable as a single-item getter, though it never explicitly contrasts itself with other single-entity getters such as ud_get_domain or ud_get_name.

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?

Explicitly states the triggering condition: 'Use it when someone asks about one trend: how it grew and its key words.' There are no when-not conditions or named alternatives, but the use context is unambiguous enough to route correctly.

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