Skip to main content
Glama
Sign In

SuVerse

by io.github.sudzikcoin
OverviewDiscussionsAdmin

One thing in full, with its price checked again right now

get_offering
Read-only

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_offering"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesthe offering id from search_catalog

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations it discloses the per-business rate limit (at most once every ten minutes), the caching semantics signalled by `from_cache` and `checked_at`, and the failure shape `ok: false` for listings without a single-item endpoint. It also tells the agent how to pass `action_url` through with the ref intact.

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-loaded with purpose and the live-check behaviour, then the rate-limit caveat and the failure mode. The closing pointer to the server instructions and the repeated safety caveats are somewhat verbose but not wasteful.

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?

There is no output schema, yet the description names the key return signals (`live_check`, `from_cache`, `checked_at`, `ok`, `action_url`), so an agent knows what to read back and how to handle the stale-cache case.

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 coverage is 100% and the single `id` parameter is already documented as 'the offering id from search_catalog', so the description adds little beyond confirming that the call returns that one offering.

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?

It states a specific verb and resource ('One offering in full') plus the distinguishing behaviour ('ONE live request to the shop asking for that item's price and stock right now'), which separates it cleanly from the bulk search_catalog path implied by the `id` parameter.

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 gives an explicit trigger ('Call it before you quote a price to a person') and a when-not case ('A price list, a menu or a quote form has no single-item door'). It does not explicitly name which sibling tool to use instead for bulk lookups, which keeps it short of 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