Skip to main content
Glama

dynadot_get_auction_bids

Fetch the bid history for a specific auction to review bidding activity; requires auction-API access.

Instructions

Get the bid history for an 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_bids"
  }
}

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.9/5.0
Behavior2/5

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

With no annotations, the description carries the full disclosure burden, yet it only adds the auction-API access prerequisite. It does not state whether access is read-only, whether bids are paginated or capped, whether it fails for closed or backorder auctions, or what the response looks like; usage guidance is therefore materially incomplete.

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

Conciseness4/5

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

Two short sentences, both doing work: one for function, one for the prerequisite, and the function comes first. Nothing is padded, though the brevity borders on under-specification rather than tightness.

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 tool with no annotations, no output schema, and zero schema description coverage, the definition is too thin. An agent cannot tell what the bid history contains, how it is bounded, or what happens when the auction is closed or inaccessible.

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?

There is a single parameter (auctionId) at 0% schema coverage, and the description only implies through 'for an auction' that it identifies the auction. It adds no detail about the accepted format, whether numeric IDs and string IDs are equivalent (the schema allows both), or where to obtain a valid ID.

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 the bid history for an auction.' That distinguishes it from siblings such as dynadot_get_auction_details (metadata) or dynadot_get_open_auctions (listings), though it never names those siblings or explicitly contrasts itself with them.

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?

The one piece of usage guidance, 'requires auction-API access,' is a real prerequisite, but it does not say when to choose this tool over dynadot_get_auction_details, nor whether it works for open versus closed auctions. Usage is implied rather than specified.

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