Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

One sales series by day, week or month, oldest first

ud_list_market_sales_series
Read-onlyIdempotent

Retrieve market sales as a time series by day, week, or month, ordered oldest first, to chart sales trends or compare periods. Specify the period with kind.

Instructions

One sales series by day, week or month, oldest first. Use it when someone wants sales over time, to chart them or compare periods. Pass kind (such as week).

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": {
      "kind": "<kind>"
    },
    "name": "ud_list_market_sales_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYesThe period: `day`, `week` (from the Monday) or `month`.
fieldsNoComma-separated top-level keys to keep: periodStart, count, meanUsd, medianUsd, comCount, aiCount.

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. Changed2 schema fields changedv0.1.5
    • changedOutput schema / properties / links / properties / details / description
      Previous value: -"The public Unique Domains page about the subject."New value: +"The public Unique.domains page about the subject."
    • changedOutput schema / properties / links / properties / product / description
      Previous value: -"The Unique Domains page that opens what a refusal named."New value: +"The Unique.domains page that opens what a refusal named."
  2. 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, so the safety profile is fully covered without the description. The description adds one genuine behavioral fact beyond that — results are ordered oldest first — but says nothing about series length, history range, truncation, or how the series is aggregated, which matters for a charting use case.

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, front-loaded with what the tool returns and followed by the use case. Slight redundancy in restating the period granularity already in the title and schema, but no sentence is wasted.

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, return shape need not be explained, and both parameters are fully described in the schema. The description covers purpose, the charting/comparison use case, and ordering, leaving only minor gaps such as how far back the series extends.

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 `kind` enum already documents day/week/month with the Monday-start convention, so the schema does the heavy lifting. The description's note about `kind` ("such as week") restates rather than extends that, and the `fields` projection parameter is never mentioned.

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 a specific resource (a sales series) and its two defining dimensions: aggregation period (day/week/month) and ordering (oldest first). That is enough for an agent to know what it returns, though it never explicitly distinguishes itself from siblings like ud_list_market_sales_endings or ud_list_market_sales_movers.

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?

"Use it when someone wants sales over time, to chart them or compare periods" gives clear situational context, and the pointer to `kind` tells the caller what to supply. It lacks any when-not guidance or named alternative, so an agent must infer the boundary against the endings/movers siblings on its own.

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