Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

One venue's profile with its verified listing terms

ud_get_venue
Read-onlyIdempotent

Retrieve one marketplace or parking service's profile and verified listing terms by ID, including commission details.

Instructions

One venue's profile with its verified listing terms. Use it when someone asks about one marketplace's or parking service's terms, such as its commission. Pass id (such as afternic).

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": {
      "id": "<id>"
    },
    "name": "ud_get_venue"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesA parking catalog id (`afternic`, `atom`, `sedo`, `dan`, ...).
fieldsNoComma-separated top-level keys to keep: slug, name, kind, ianaId, accredited, homepageUrl, siteUrl, logoUrl, footprint, footprintDay, listingTerms.

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 read-only, idempotent, non-destructive, and closed-world behavior, so the safety profile is covered. The description adds only that the listing terms are 'verified' and gives an example id value; it says nothing about data freshness, errors for unknown ids, or return shape (covered by the output schema). This is adequate but not rich.

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 three short, front-loaded sentences with no filler. The first sentence duplicates the title exactly, which is minor waste, but the rest is efficient. Structure is clear and easy to scan.

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 simple read-only getter with an output schema and full input-schema coverage, the description supplies enough context to select and call it. It gives the use case and an id example. It could mention the optional `fields` parameter or clarify what a 'venue' is, but those are minor given the structured data.

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 both parameters are fully documented there. The description only reiterates the required `id` parameter and gives the same kind of example already present in the schema, while omitting the optional `fields` parameter entirely. Baseline 3 is appropriate because the schema does the heavy lifting.

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 and scope: one venue's profile and verified listing terms. It distinguishes a single-venue lookup from broader list/search tools by phrasing, but it never names a specific sibling alternative. The only gap is the lack of an explicit verb and sibling routing.

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 concrete when-to-use condition: when someone asks about one marketplace's or parking service's terms, such as commission. It does not state when not to use this tool or name the list-venues sibling as an alternative. Still, the guidance is clear enough for selection.

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