Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Latest published daily edition of one page

ud_get_latest_edition
Read-onlyIdempotent

The latest published daily edition of one page. 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 observed

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and openWorldHint=false, so the safety profile is fully covered without the description. Beyond that, the description adds nothing — it does not explain what 'latest' means when today's edition is unpublished, whether a stale edition is returned, or how freshness is determined.

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 short sentences, front-loaded with the resource. The second sentence is close to redundant with the required `persona` parameter already documented in the schema, but nothing is bloated.

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, full annotation coverage and 100% schema description coverage, most of the burden is carried elsewhere and the tool is simple (one required enum parameter). The only meaningful gap is that 'latest' semantics and the absence-of-edition case remain unexplained.

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 coverage is 100%, so both parameters (including the `fields` projection list) are fully documented in the schema. The description's 'such as founder' actually understates the enum's closed set of founder/investor, so it adds no meaning and is slightly less precise than the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('latest published daily edition of one page'), but 'one page' is vague and the phrasing largely restates the title verbatim. It never distinguishes this tool from the sibling ud_get_edition, which appears to return an edition by a different selector, so an agent must open the schema to tell them apart.

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?

The only guidance is 'Pass `persona` (such as founder)', which is a parameter instruction rather than a when-to-use rule. There is no mention of when to prefer this over ud_get_edition, no note about what happens if no edition has been published yet, and no exclusions at all.

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