Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Parking and marketplace venues with a profile and their rounded footprint

ud_list_venues
Read-onlyIdempotent

The parking and marketplace venues with a profile and their rounded footprint. 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 observed

TDQS

C2.6/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 safety needs no restating. Beyond that the description adds only "Takes no input," which is inaccurate for a schema containing an optional fields parameter, and it says nothing about result set size, ordering, or whether every venue is returned.

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?

Two short sentences, front-loaded with the subject matter, which is structurally sound. The second sentence is not just wasted but misleading, so brevity does not translate into value here.

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?

An output schema exists and rich annotations cover safety, so the definition does not need to describe return values. What remains missing for a list tool in a family of ~50 siblings is the conceptual content of a "venue" and its relationship to ud_get_venue and ud_list_market_auction_venues.

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 single fields parameter enumerates every valid top-level key, so the schema carries parameter meaning on its own. The description does not even acknowledge that parameter, and its "Takes no input" line actively points the opposite direction, though the enumerated schema limits the real damage.

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 description names the resource (parking and marketplace venues) and a distinguishing filter ("with a profile"), implying a subset of all venues. But "venue" is never defined, the listing verb only appears in the tool name, and the nearby sibling ud_list_market_auction_venues is never distinguished from this one.

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?

There is no when-to-use guidance at all: nothing says to call this instead of ud_get_venue for a single record or ud_list_market_auction_venues for auction data. The only stated guidance is "Takes no input," which is usage-adjacent but factually wrong given the optional fields parameter.

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