Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Parking and marketplace venues with a profile and their rounded footprint

ud_list_venues
Read-onlyIdempotent

Lists parking and marketplace venues with profile fields and rounded footprints to show which services list domain names and how many. Takes no input.

Instructions

The parking and marketplace venues with a profile and their rounded footprint. Use it when someone asks which marketplaces or parking services list names, and how many. Takes no input.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ud_list_venues"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: slug, name, kind, ianaId, accredited, homepageUrl, siteUrl, logoUrl, footprint.

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

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds little beyond that and states 'Takes no input,' which is misleading because the schema includes an optional fields parameter. Still, the optional parameter means a no-input call is possible, so it is not a direct annotation contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the resource, but its first sentence largely restates the title. The final sentence 'Takes no input' is both misleading and wasteful given the optional fields parameter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema and rich annotations, the description does not need to explain return values or safety behavior. However, for a list tool with an optional projection parameter, it should acknowledge that fields can be supplied rather than claiming it takes no input. The usage cue is helpful but incomplete without sibling differentiation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the fields parameter is fully documented in the schema. The description does not add any parameter meaning and instead says 'Takes no input,' which conflicts with the presence of an optional fields parameter and could cause an agent to overlook it.

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 identifies the resource as parking and marketplace venues with profiles and a rounded footprint, and says it is for listing names and counts. It is reasonably clear, but it does not explicitly differentiate itself from the sibling ud_list_market_auction_venues or clarify what a 'profile' or 'rounded footprint' means.

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?

It gives a usage cue: 'Use it when someone asks which marketplaces or parking services list names, and how many.' However, it offers no when-not-to-use guidance and does not name or distinguish alternatives, leaving the agent to infer selection among many list tools.

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