Skip to main content
Glama

Everything AREMES and RSMAD sell, with prices and how to buy

get_offers
Read-only

The full list of offers from Ryan Seslow Art & Design LLC (AREMES ENTERPRISES and RSMAD): AREMES Worlds (a walkable exhibition of your own art), spaces for license, 3D model and image licenses, the AR Asset Mega Pack, RSMAD membership, museum passes and more. Returns each offer with what it is, its page, prices and how a person or an agent buys it. People pay by card at Stripe checkout.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_offers"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description adds real value beyond that by stating what the response contains (each offer's identity, page, prices, purchase path) and how payment works (card via Stripe checkout). That return-shape and payment context is useful given there is no output schema, though it does not discuss pagination or scope limits.

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?

Two sentences, front-loaded with the resource and followed by the offer enumeration and return contents. The parenthetical brand expansion and long comma-separated list are dense but each item conveys product scope rather than filler.

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 parameters, read-only/non-open-world annotations, and no output schema, the description carries the burden of describing the return and does so (offers, pages, prices, purchase method, Stripe checkout). A short note on result size or whether all offers are always returned would close the remaining gap.

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?

The tool takes zero parameters, so per the baseline there is no parameter semantics to compensate for; the schema coverage is complete and the description makes clear the call is argument-free by describing a global catalog dump.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('the full list of offers') and enumerates the catalog's contents (AREMES Worlds, license spaces, 3D/image licenses, Asset Mega Pack, membership, museum passes), which lets an agent understand this is the umbrella catalog versus the narrower sibling listers. It does not explicitly name a sibling to distinguish against, keeping it just short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

Use is implied rather than stated: 'the full list' suggests browsing everything for sale, and the mention of how a person or agent buys hints at the purchase-discovery use case. There is no explicit when-to-use, when-not-to-use, or pointer to alternatives such as get_membership or list_spaces for narrower lookups.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources