Skip to main content
Glama
Sign In

Buy-Box

by io.github.tthompson0808
OverviewDiscussionsAdmin

Send feedback to the Buy-Box team

send_feedback

Send a bug report, idea or comment about Buy-Box itself to its developers. Use it only when the user asks to leave feedback. Send only what the user wrote or approved, and show them the text first. Never attach their buy box contents or other personal details. At most 10 per day.

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": {
      "message": "<message>"
    },
    "name": "send_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNo
contactNoOptional email for a reply. Only if the user offers one.
messageYesThe feedback text, up to 2,000 characters.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior1/5

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

The description says the tool sends a message 'to its developers,' i.e., transmission to an external party, while the annotations declare openWorldHint=false (closed-world interaction). That is a direct contradiction. The otherwise useful disclosures (10/day rate limit, show-text-first, no personal details) cannot offset an annotation mismatch.

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?

Five short sentences, front-loaded with what the tool does, then when to use it, then consent and privacy constraints, then the rate limit. No redundant or filler text.

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 and only three parameters, the description covers the essentials an agent needs: purpose, consent workflow, content restrictions, and the daily limit. Its one completeness failure is the open-world mismatch with the annotations.

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

Parameters4/5

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

Schema coverage is moderate (67%); the schema defines contact and message but leaves `kind` undocumented. The description adds meaningful semantics beyond the schema: the message must be only what the user wrote or approved, no buy-box contents or personal details may be attached, and contact is conditional on the user offering it.

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?

States a specific verb (send), the exact content types (bug report, idea, comment about Buy-Box), and the recipient (its developers). This is unmistakably distinct from the sibling CRUD tools (get/set/delete/export_buy_box, score_candidates), none of which transmit feedback.

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?

Explicitly scopes invocation: 'Use it only when the user asks to leave feedback,' which is both a when-to-use and a when-not-to-use rule. It also requires showing the user the text and only sending approved content, removing ambiguity about consent.

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

All Buy-Box 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