Skip to main content
Glama

CommerceBook

by ai.commercebook
OverviewDiscussionsAdmin

Read the market

commercebook_market
Read-onlyIdempotent

Read the market with no key: what is for sale, what buyers ask for, a seller record, reach and shipping. Actions (the activity each needs):

  • book (no key): what is for sale and what buyers ask for, by category, right now.

  • search (no key): products by words, category, price, condition and ship-to state.

  • product (no key): one product (lot_id): count, condition, photos, shipping, offers.

  • seller (no key): a seller record (seller_slug): tier, rates, ratings, products.

  • requests (no key): the open requests to buy, with quantity and the most each buyer pays.

  • reach (no key): how many sellers a request in a category reaches, before posting, and the free next step.

  • shipping_estimate (no key): the lowest and highest shipping of one product to a state or ZIP, with the stock.

  • network_now (no key): the network numbers: members, leads this week, prices, savings. Send action and its arguments.

Input Schema

NameRequiredDescriptionDefault
qNoFor search, requests. Words; a product matches any of them as a whole word of the title, the category, the specifics, the brand or the part number (a plural ending s or es matches too), and more matched words rank higher.
qtyNoFor reach, shipping_estimate.
slugNoFor seller. The older name of seller_slug, still accepted.
limitNoFor search, requests.
queryNoFor search. The same as q, for an agent that names it query.
stateNoFor search, shipping_estimate. Two-letter state the goods ship to.
actionYesThe action to run.
lot_idNoFor product, shipping_estimate. The lot_id of a search item.
categoryNoFor search, requests, reach. A category key, exact (for example packaging, tools, home_garden). commercebook_market action book lists every key with its products and open requests.
conditionNoFor search.
max_priceNoFor search.
min_priceNoFor search.
seller_slugNoFor seller. The seller_slug of a search item or a product.
destination_zipNoFor shipping_estimate. The five-digit ZIP the goods go to; the state is read from it. Send this or state.
destination_stateNoFor reach. A two-letter state.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"For search, requests, reach. A category key, exact (for example packaging, tools, home_garden). commercebook_market_book lists every key with its products and open requests."New value: +"For search, requests, reach. A category key, exact (for example packaging, tools, home_garden). commercebook_market action book lists every key with its products and open requests."
    • addedInput schema / properties / destination_zip
      Added value: +{
+  "description": "For shipping_estimate. The five-digit ZIP the goods go to; the state is read from it. Send this or state.",
+  "pattern": "^\\d{5}(-\\d{4})?$",
+  "type": "string"
+}
    • changedInput schema / properties / q / description
      Previous value: -"For search, requests. Words; each must match a whole word of the title, brand, part number or description (a plural ending s or es matches too)."New value: +"For search, requests. Words; a product matches any of them as a whole word of the title, the category, the specifics, the brand or the part number (a plural ending s or es matches too), and more matched words rank higher."
    • addedInput schema / properties / query
      Added value: +{
+  "description": "For search. The same as q, for an agent that names it query.",
+  "maxLength": 200,
+  "type": "string"
+}
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely useful context the annotations don't carry: every action needs 'no key' (auth-free), and each action's return subject is sketched. Rate limits, result caps and pagination behavior are still unstated.

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?

The purpose is front-loaded and the action list is scannable, with each line earning its place. The phrase 'no key' is repeated eight times after being stated once up front, which is mild redundancy in an otherwise tight definition.

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 15-parameter dispatcher with no output schema and only one required field, the description does the important work: it names every action and what each returns, which the schema's flat property list does not. It stops short of covering defaults (limit bounds), how qty interacts with reach versus shipping_estimate, and whether searches paginate.

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% and every parameter already names the actions it applies to, so the description's '(lot_id)', '(seller_slug)' annotations largely duplicate structured data. 'Send action and its arguments' adds no syntax or default information beyond the schema; baseline 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 opening line states the resource and scope ('read the market with no key') and the enumeration then gives a concrete verb+output for each of the eight actions (book, search, product, seller, requests, reach, shipping_estimate, network_now). Nothing here overlaps with siblings like commercebook_account_start or commercebook_capabilities, so an agent can route correctly without opening the schema.

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?

Each action line describes the situation that selects it, and 'reach ... before posting' is an explicit sequencing hint. What's absent is any exclusion or cross-tool routing — it never says when to prefer a sibling tool (e.g. commercebook_tool_search or commercebook_start) or when this tool is the wrong choice.

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

All CommerceBook toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources