Skip to main content
Glama

Gunbroker

by io.github.pipeworx-io

Gunbroker Seller Orders

gunbroker_seller_orders
Read-onlyIdempotent

List the authenticated seller's sold orders (GunBroker /OrdersSold) — order IDs, buyers, item titles, totals, payment and shipping status. Seller tool: needs a GunBroker developer key (_apiKey) PLUS the seller's GunBroker username and password, which are exchanged for a short-lived access token on each call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
_apiKeyYesGunBroker developer key (X-DevKey). Required.
PageSizeNoResults per page (default 25, max 300).
passwordYesGunBroker seller account password. Required.
usernameYesGunBroker seller account username. Required.
PageIndexNoPage number, 1-based (default 1).
TimeFrameNoGunBroker time-frame filter for sold orders (e.g. recent N days). Optional.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "_apiKey": "your-gunbroker-api-key",
+    "password": "seller_password",
+    "username": "seller_username"
+  },
+  {
+    "PageIndex": 1,
+    "PageSize": 100,
+    "TimeFrame": 30,
+    "_apiKey": "your-gunbroker-api-key",
+    "password": "seller_password",
+    "username": "seller_username"
+  }
+]
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=true. The description adds valuable behavioral context: each call requires credentials exchanged for a short-lived access token. There are no contradictions with annotations, and the description provides sufficient extra detail for safety and idempotency considerations.

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?

The description is two sentences: the first clearly states the action and output, and the second specifies auth requirements. Every sentence adds necessary information without redundancy or fluff, making it highly concise and well-structured.

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?

Given no output schema, the description compensates by listing key output fields (order IDs, buyers, totals, payment/shipping status). It explains the auth mechanism well. However, it does not mention pagination behavior or the TimeFrame filter, which would be helpful for completeness. Overall, it is adequate but could include a note about paging.

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 coverage is 100% with full parameter descriptions, setting a baseline of 3. The description adds context for the authentication parameters (_apiKey, username, password) explaining the token exchange, but does not mention pagination parameters (PageSize, PageIndex) or TimeFrame. This addition is marginal, so a score of 3 is appropriate.

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 explicitly states 'List the authenticated seller's sold orders' and names the endpoint (GunBroker /OrdersSold). It lists the output fields (order IDs, buyers, etc.), which clearly specifies the resource and action. The title 'Gunbroker Seller Orders' further distinguishes from sibling tools like gunbroker_get_item and gunbroker_search_items.

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

Usage Guidelines4/5

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

The description clearly indicates the tool is for sellers and requires authentication each call (short-lived token), establishing a clear usage context. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention when not to use it, such as for buyer orders or other search scenarios.

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

All Gunbroker toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources