Skip to main content
Glama

dynadot_get_auction_details

Retrieve details for a single auction using its auction ID, so you can inspect listing data when auction-API access is enabled.

Instructions

Get details for a single auction. NOTE: requires auction-API access.

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": {
      "auctionId": "<auctionId>"
    },
    "name": "dynadot_get_auction_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
auctionIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv3.0.0
    • removedInput schema / properties / auctionId / anyOf
      Removed value: -[
      -  {
      -    "type": "number"
      -  },
      -  {
      -    "type": "string"
      -  }
      -]
    • addedInput schema / properties / auctionId / type
      Added value: +[
      +  "number",
      +  "string"
      +]
  2. First observedv2.0.1

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose one genuinely useful behavioral fact: auction-API access is required. Beyond that it says nothing about failure modes for an invalid or non-auction ID, rate limits, or what the returned detail set contains.

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

Conciseness5/5

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

Two short sentences with the purpose front-loaded and the access prerequisite clearly flagged. No filler or redundancy.

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?

For a simple one-parameter read tool this is close to adequate, and the access note is valuable. But with no annotations, no output schema, and an undocumented identifier parameter, an agent still cannot tell what it will receive or how to source a valid auctionId.

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 description coverage is 0% and the single required parameter, auctionId, is not mentioned in the description at all — not its accepted types (number or string), nor where to obtain a valid ID. The one sentence of description adds no meaning over the bare 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 names a specific verb and resource ("Get details for a single auction") and the word "single" implicitly separates it from the sibling list tools like dynadot_get_open_auctions and dynadot_get_closed_auctions. It does not name an alternative explicitly, so it stops short of a 5.

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?

Usage is only implied: an agent can infer this is the per-record lookup to use once it already has an auction ID, as opposed to the listing tools. There is no explicit when-to-use, when-not, or named alternative, so guidance is minimal but present.

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