Buy-Box

by io.github.tthompson0808

Overview Discussions Admin

Create or update buy box

set_buy_box

Destructive

Create or update the buy box for a category. Any field names are allowed.

Call get_buy_box first and REUSE the field names already in the box.

criteria: fields to set; each value you send replaces that field's value. A value of null deletes that field.
add: {field: [items]} appends items to any list field (created if missing, duplicates skipped). Use this to add one item without resending the whole list.
remove: {field: [items]} removes items from a list field (case-insensitive for text).
remove_fields: [field, ...] deletes whole fields.
replace=true: start from an empty box instead of merging. Order within one call: remove_fields, then criteria, then add, then remove. Server fields (_meta, requires_confirmation, last_updated) are ignored in criteria.
expected_revision: pass _meta.revision from your last get_buy_box so you don't overwrite another agent's change. If the box changed since, nothing is saved and the error returns the current box: re-read it and ask the user before writing again if a field you were changing was changed. Use 0 to create a box only if it doesn't exist. Field names are normalized to snake_case. If a new field looks like an existing one (e.g. max_miles vs max_mileage), it is saved and _meta.warnings names the existing field: tell the user and fix it with remove_fields. Do not store health details, account numbers, or passwords. Returns the saved box.

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": {
      "category": "<category>"
    },
    "name": "set_buy_box"
  }
}

Input Schema

Name	Required	Description	Default
`add`	No
`remove`	No
`replace`	No
`category`	Yes
`criteria`	No
`remove_fields`	No
`expected_revision`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 29, 2026

addedInput schema / properties / expected_revision

Added value: +{
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}

First observedOct 28, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the annotations, the description explains merge versus replace behavior, null deletion, append/remove semantics with duplicate skipping, case-insensitive removal, operation ordering, ignored server fields, field normalization, _meta.warnings, and conflict behavior with expected_revision. These details are consistent with destructiveHint=true and idempotentHint=false, not contradictory.

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 long but appropriately so for a seven-parameter mutation tool with complex merge semantics. It is front-loaded with purpose and the get-first instruction, then organized into bullets that make each behavior easy to scan, with no obvious filler.

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

Completeness5/5

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

For a complex write tool with no output schema and 0% schema description coverage, the description covers the missing pieces: operation semantics, conflict handling, privacy constraints, warnings, and what the tool returns. An agent has enough information to invoke it correctly and handle common failure modes.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry the parameter burden, and it does: it documents criteria, add, remove, remove_fields, replace, expected_revision, and the category context. It also adds crucial semantics not present in the schema, such as null deleting a field, add appending items, remove being case-insensitive, and replace starting from an empty box.

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 opens with a specific verb and resource: 'Create or update the buy box for a category.' It also distinguishes this write operation from the sibling read tool by instructing the agent to call get_buy_box first, so an agent can select it 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 Guidelines5/5

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

It explicitly says to call get_buy_box first and reuse existing field names, explains when expected_revision should be passed, and specifies that expected_revision=0 should be used only when creating a box that does not exist. It also gives conflict-handling guidance: re-read and ask the user before writing again if the relevant field changed.

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

All Buy-Box tools Inspect

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.