Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

One dated published edition of one page

ud_get_edition
Read-onlyIdempotent

One dated published edition of one page. Pass persona (such as founder) and date (such as 2026-11-02).

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>",
      "date": "<date>"
    },
    "name": "ud_get_edition"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateYesThe edition day, UTC.
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, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that: no not-found behavior for an unpublished date, no mention of how previousDate/nextDate chaining works, no note that fields filtering affects only top-level keys.

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 with no filler, and the parameter guidance is front-loaded after the resource statement. It is efficient, though the first sentence largely duplicates the title rather than using the space to add differentiating information.

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?

An output schema exists, so return values need no explanation, and the annotations cover safety. What remains missing is modest but real: sibling differentiation from the 'latest edition' tool and failure behavior for an unpublished date. For a simple two-required-parameter read tool this is close to adequate.

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 all three parameters are already documented, including the persona enum meanings. The description's example values ('founder', '2026-11-02') merely restate the schema, and it says nothing about the optional `fields` projection parameter, so it does not exceed the baseline.

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 phrase 'One dated published edition of one page' names the resource and implies a specific-date lookup, which is more informative than the title alone only marginally. It is a noun phrase with no verb and never distinguishes itself from the obvious sibling ud_get_latest_edition, so an agent must infer that 'dated' means 'you supply the date, it is not the newest'.

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 description only says which parameters to pass; it gives no condition for choosing this tool over ud_get_latest_edition or ud_get_agenda, and no note about what to do if the requested date has no published edition. Usage is implied by the name rather than stated.

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