Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Every enum the payloads use, read from the code catalogs

ud_get_meta_enums
Read-onlyIdempotent

Every enum the payloads use, read from the code catalogs. 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_get_meta_enums"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: statuses, lifecycles, eppStatuses, lookupStates, wordShapes, wordOrigins, tldKinds, agendaCategories, eventCategories, editionLanes, changeEventTypes, changeEventSubjects, auctionVenues, parkingServices.

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?

The annotations already establish read-only, idempotent, closed-world, non-destructive behavior. The description adds only that enums come from code catalogs, and its claim that the tool takes no input is inaccurate given the optional 'fields' parameter; it does not explain default behavior when fields is omitted.

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-loaded, but the second sentence is factually incorrect and therefore does not earn its place. 'Payloads' is also slightly vague, though the first sentence remains efficient.

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

Completeness2/5

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

An output schema exists, so return values need not be explained. But for a tool with one optional filtering parameter, the description omits the ability to trim the result with 'fields' and instead denies input entirely, leaving an agent with an incomplete picture of how to invoke it optimally.

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?

The schema fully documents the optional 'fields' parameter and its accepted keys, so baseline would be 3. However, the description explicitly says 'Takes no input', contradicting the schema and providing negative value about parameter usage rather than adding meaning beyond the schema.

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 states a specific resource and source: every enum used by payloads, read from code catalogs. This is clear enough to understand what the tool returns, though it does not differentiate from nearby meta tools or explain how the enums are organized.

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 guidance on when to use this tool versus alternatives such as ud_list_meta_datasets or ud_get_meta_freshness. Worse, 'Takes no input' implies no parameters are available, which conflicts with the optional 'fields' parameter and could steer the agent away from a useful filtering option.

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