Skip to main content
Glama
Sign In

Reverb

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Reverb Shop

reverb_shop
Read-onlyIdempotent

Reverb.com seller profile by shop slug: shop name, location, feedback count and rating, preferred-seller status, return policy and shipping posture. Answers "who is this seller and what is their track record" for a listing found via reverb_search.

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": {
      "shop_slug": "guitar-sauce-italy"
    },
    "name": "reverb_shop"
  }
}

Input Schema

NameRequiredDescriptionDefault
shop_slugYesShop slug, e.g. "guitar-sauce-italy" (the `shop_slug` from reverb_search)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds valuable context about what the profile contains and frames the tool's purpose, going beyond what annotations encode. No contradiction with annotations.

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?

Two sentences with no filler. The first sentence packs the resource and returned fields compactly; the second adds the use-case question. The key identifying information is front-loaded.

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?

With one fully-documented parameter, rich annotations covering safety, and a description that lists output fields and the source context (reverb_search), the agent has everything needed to call the tool correctly. No output schema is needed since the field list is already in the description.

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?

The input schema fully documents shop_slug with an example and a cross-reference to reverb_search; the description adds no additional parameter semantics beyond that. At 100% schema description coverage, a 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 description opens with 'Reverb.com seller profile by shop slug' and enumerates the specific fields returned (shop name, location, feedback count and rating, preferred-seller status, return policy, shipping posture). The second sentence frames it as answering 'who is this seller and what is their track record,' clearly distinguishing it from sibling tools like reverb_search and reverb_listing.

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?

It explicitly ties usage to a prior reverb_search: 'for a listing found via reverb_search.' This gives the agent a clear trigger condition. It doesn't enumerate exclusions (e.g., when to prefer reverb_listing over this tool), so it lacks explicit alternatives, but the context is unambiguous.

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

All Reverb 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