Skip to main content
Glama
Sign In

SuVerse

by io.suverse.www
OverviewDiscussionsAdmin

One thing in full (synonym of get_offering)

get_product
Read-only

SYNONYM of get_offering, kept for agents that already know this name. A «product» is just an offering whose kind is product; the same id works in both.

Free. One offering in full, with ONE live request to the shop asking for that item’s price and stock right now (live_check). Call it before you quote a price to a person: a catalogue read yesterday is yesterday’s price. One business is asked at most once every ten minutes however many of its offerings you open, so walking a shop is one request and not twenty; from_cache and checked_at say which. A price list, a menu or a quote form has no single-item door to ask (ok: false with the reason) and the stored reading stands with its date.

Hand action_url to the user as it is, ref=suverse included. Follow the server instructions «HOW TO USE THE SUVERSE CATALOG»: results are candidates, not proof; keep reading, quoting, requesting and ordering separate; nothing is sent to an owner, booked, ordered or paid without the user’s permission.

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": {
      "id": "<id>"
    },
    "name": "get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe offering id from search_catalog

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnly/openWorld annotations: discloses a live outbound request to the shop, a per-business rate limit of one request per ten minutes, that walking a shop collapses to one request, that from_cache/checked_at reveal freshness, and that single-item-less sources return ok:false with a reason. It also warns against treating results as proof and mandates passing action_url through unchanged including ref=suverse.

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?

Front-loads the synonym relationship and then the core behavior, with mostly load-bearing sentences (the pricing rationale justifies the frequency warning). Some redundancy in the closing server-instructions recap and a few meta asides that could be trimmed.

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?

No output schema exists, yet the description names the key return fields (price, stock, from_cache, checked_at, ok) and the failure mode, so an agent knows what to expect and how to report it. It also covers the permission boundary for downstream actions, which is essential for a read tool that feeds quoting/ordering flows.

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 100% and the single parameter is already documented as "the offering id from search_catalog", so the baseline would be 3. The description adds real meaning by clarifying the id is interchangeable with get_offering's, which is not derivable from the schema alone.

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 precisely what it returns — "One offering in full" — plus the side effect of a live price/stock check, and explicitly frames itself as a synonym of get_offering ("a «product» is just an offering whose kind is `product`; the same id works in both"). An agent can distinguish it from the sibling without opening either 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?

Gives clear trigger guidance: "Call it before you quote a price to a person: a catalogue read yesterday is yesterday's price." It also explains the get_offering equivalence so the choice between the two is trivial. It stops short of stating when NOT to call it (e.g. bulk/browse cases) beyond the price-list edge case, so not quite a 5.

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

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