Skip to main content
Glama

Bonanza Search

bonanza_search
Read-onlyIdempotent

Search active Bonanza marketplace listings by keyword (Bonapitit findItemsByKeywords). Requires a Bonanza API devID. No sold data, orders are seller-scoped on this API.

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": {
      "_apiKey": "your-bonanza-devid",
      "keywords": "vintage brass lamp",
      "entries_per_page": 10
    },
    "name": "bonanza_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
keywordsYesSearch keywords, e.g. "vintage brass lamp"
sort_orderNoBestMatch (default) | CurrentPriceHighest | PricePlusShippingLowest | EndTimeSoonest
page_numberNoPage number, 1-based (default 1)
entries_per_pageNo1-100 (default 25)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds real value nonetheless: it discloses the devID auth requirement, the absence of sold/completed data, and that order data is seller-scoped on this API.

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?

Three compact sentences with the primary action front-loaded and no filler. The trailing clause about orders being seller-scoped is slightly cryptic for a listing-search tool, but it costs little space.

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?

For a read-only search with no output schema, the description covers auth requirements and data scope, which are the main things an agent needs before calling. It omits result-volume or pagination behavior, a minor gap given the schema already documents page_number and entries_per_page.

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%, including keyword examples, sort_order options, and paging defaults, so the schema does the heavy lifting. The description contributes no additional parameter meaning beyond "by keyword", which is the baseline 3.

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 ("Search active Bonanza marketplace listings by keyword") and even cites the underlying endpoint (Bonapitit findItemsByKeywords). "By keyword" implicitly contrasts with the sibling bonanza_search_by_category, though it never names that alternative directly.

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 implied by "active listings" and "by keyword", and the negative constraint "No sold data" rules out a use case. However, it gives no explicit when-to-use/when-not guidance or named alternative, so an agent must infer that category browsing belongs to the sibling tool.

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.