Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

One venue's profile with its verified listing terms

ud_get_venue
Read-onlyIdempotent

One venue's profile with its verified listing terms. 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 observed

TDQS

A3.5/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. The description adds only that the listing terms are 'verified', a small content hint; it says nothing about freshness, caching, or error behavior when an unknown id is supplied.

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 what is returned, followed by the call hint. The second sentence largely duplicates information the schema already provides, so it is not maximally economical, but there is no filler or rambling.

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 and annotations are rich, so the description need not explain return values or safety. For a two-parameter read tool this is close to sufficient; the only real gap is the absent cross-reference to ud_list_venues for id discovery and no note on behavior for an invalid id.

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% — both `id` and `fields` are documented in-schema, including enum-like examples (afternic, atom, sedo, dan) and the allowed top-level keys. The description's 'such as afternic' merely repeats an example already present in the schema, so it adds no new meaning; baseline 3 applies.

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 the resource (a single venue's profile) and its payload ('verified listing terms'), which is specific enough to distinguish it from the plural sibling ud_list_venues. It never explicitly says 'single record vs list', so the differentiation is implied by the singular phrasing rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Pass `id` (such as afternic)' gives a usage cue for the call, but there is no when-to-use/when-not guidance and no pointer to ud_list_venues for discovering valid ids or to any other venue-related tool as an alternative. Usage is implied by the parameter hint only.

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