Skip to main content
Glama

dynadot_place_auction_bid

Place a bid on an expired-domain auction using an auction ID and bid amount; auction-API access is required.

Instructions

Place a bid on an expired-domain 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>",
      "bidAmount": "<bidAmount>"
    },
    "name": "dynadot_place_auction_bid"
  }
}

Input Schema

NameRequiredDescriptionDefault
auctionIdYes
bidAmountYes

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?

No annotations are supplied, so the description carries the entire burden of disclosure. The note 'requires auction-API access' is genuinely useful context about a prerequisite, but for a financial mutation, the description does not say whether the bid commits funds, is reversible, whether the bid can be retracted, what happens if the bid is below a minimum increment, or what a success or failure response looks like.

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 with the action front-loaded and the prerequisite note clearly separated. There is no filler, though the brevity is partly under-specification rather than purely efficient packing.

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?

This is a two-parameter irreversible financial mutation with no annotations, no output schema, and zero parameter documentation. Against that complexity, the definition supplies only the action and one access prerequisite, leaving an agent without enough information to call it confidently or predict its effects.

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% for both parameters, so the description must compensate but does not. It never explains whether 'auctionId' is a numeric auction identifier or something else (the schema allows both number and string, which is ambiguous), nor what currency, format, or minimum increment applies to 'bidAmount'.

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 combination: 'Place a bid on an expired-domain auction.' An agent can tell this is a bidding action rather than a read or lookup. However, it does not distinguish itself from the sibling dynadot_place_backorder_auction_bid, which is a nearly identical action on a different auction type.

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 phrase 'expired-domain auction' implicitly scopes when to use this tool versus backorder auctions, but that distinction is only implied by the adjective. There is no explicit statement of when not to use it, no mention of the backorder-auction sibling, and no guidance on preconditions such as whether the user must already be registered for the auction.

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