Skip to main content
Glama

Us Auction Houses

us_auction_houses
Read-onlyIdempotent

Which US auction houses Pipeworx covers, and how much they currently have live, name, home state, number of open sales and total lots across them. Use to find the auctioneers active in a state or in a niche ("who runs industrial liquidations in California"), then pass the name to us_auction_events or us_auctions_search. Ranked by live lot count.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "limit": 15
    },
    "name": "us_auction_houses"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax houses (1-100, default 25).
stateNo2-letter state code of the sale location.
keywordNoFree-text matched against the house name or its sale titles.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds useful behavior beyond that: the result set is scoped to houses Pipeworx covers and is ranked by live lot count, which tells the agent how to interpret ordering. It does not mention pagination or result-size behavior, keeping it short of a 5.

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 sentences, front-loaded with what the tool returns, followed by when to use it and where to pass the output. No redundant restatement of the name or title.

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

Completeness4/5

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

With no output schema, the description correctly compensates by listing the returned fields and the sort order. The only gap is that it says nothing about result volume or how the limit interacts with ranking, which is minor for a simple three-parameter list tool.

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

Parameters3/5

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

Schema description coverage is 100%, so limit, state and keyword are already documented in the schema. The description adds only marginal meaning, mainly illustrating keyword usage through the 'industrial liquidations in California' example. Baseline 3 is appropriate when the schema carries the parameter burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (US auction houses covered by Pipeworx) and enumerates the returned fields: name, home state, open sales, total lots. It also distinguishes itself from siblings by positioning itself as the discovery step that feeds us_auction_events and us_auctions_search.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states the use case explicitly ('find the auctioneers active in a state or in a niche') with a concrete example query, and it names the downstream tools to call with the result. The routing decision is fully specified rather than implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.