Skip to main content
Glama

dynadot_get_backorder_auction_details

Retrieve details for a specific backorder auction by auction ID, so you can review its current status and information before bidding.

Instructions

Get details for a backorder auction.

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_backorder_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

C2.4/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It does not state that this is a read-only retrieval, whether authentication is required, what kind of auction details are returned, or what happens if the auction ID is invalid.

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 a single front-loaded sentence with no wasted words. However, it is under-specified rather than appropriately concise for a tool with no annotations and no output schema.

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?

For a simple one-parameter retrieval tool, the definition still lacks crucial context: what details are returned, whether the auction must be open or closed, and how the auctionId is obtained. With no annotations and no output schema, the description should do more to make the tool callable with confidence.

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

Parameters1/5

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

The single required parameter, auctionId, has 0% schema description coverage and the description adds no meaning about its expected format, source, or whether numeric and string forms differ. The description provides no parameter guidance at all.

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 verb and resource: get details for a backorder auction. It is clear what the tool does, but it does not distinguish this from sibling tools such as dynadot_get_auction_details or explain how backorder auction details differ.

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 like dynadot_get_auction_details, dynadot_get_auction_bids, or dynadot_get_open_backorder_auctions. The agent must infer the appropriate context from the name alone.

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