Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Latest daily edition of Business Ideas or Trending Domains

ud_get_latest_edition
Read-onlyIdempotent

Retrieve the current daily edition of Business Ideas or Trending Domains, returning open names tied to rising topics for a chosen founder or investor persona.

Instructions

The latest daily edition of Business Ideas or Trending Domains: trends with open names, for founders or for investors. Use it when someone wants today's name ideas from rising topics; it carries the edition's open names only. Pass persona (such as founder).

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": {
      "persona": "<persona>"
    },
    "name": "ud_get_latest_edition"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: persona, date, publishAt, trendCount, nameCount, openCount, previousDate, nextDate, trends.
personaYesBusiness Ideas (`founder`) or Trending Domains (`investor`).

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

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false, and openWorldHint false, covering the safety profile. The description adds useful scope that the edition carries open names only, but it does not discuss freshness edge cases, authorization needs, or behavior when no edition exists.

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?

The description is front-loaded and two sentences long with no significant waste. The parenthetical persona example is slightly redundant with the enum in the schema, but the structure remains efficient.

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?

For a low-complexity read-only tool with two parameters, full schema coverage, annotations, and an output schema, the description covers purpose, usage context, persona selection, and the open-names scope. It does not explain the fields parameter, but the schema already does so adequately.

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%, and the schema already documents the persona enum and fields parameter. The description only says to pass persona (such as founder), which adds little beyond the schema and omits guidance on the fields parameter, so the baseline of 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?

The description clearly identifies the resource as the latest daily edition of Business Ideas or Trending Domains and specifies that it contains trends with open names. It distinguishes founder versus investor editions, but does not explicitly differentiate itself from the sibling ud_get_edition tool.

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?

It gives a clear usage context: use when someone wants today's name ideas from rising topics. It does not state when not to use it or name an alternative tool, so it stops short of full routing guidance.

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