Skip to main content
Glama

RSMAD museum membership

get_membership
Read-only

RSMAD membership opens the Members' Wing, four galleries on the second floor of AREMES HQ. Annual $50, Seasonal (6 months) $30 and Quarterly (3 months) $18 also include early access to new original works and 10% off original art; the Day Pass ($5) opens the Members' Wing for one day. Returns the tiers with their Stripe checkout links. After paying, the member lands on a welcome page that opens the doors.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, closed-world operation. The description adds useful behavioral context beyond that: it returns tiers with Stripe checkout links and explains the post-payment welcome-page flow, which helps an agent understand what happens after selection.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description front-loads atmospheric membership benefits and detailed pricing before stating the core return behavior. The pricing details may be useful, but the final sentence about the welcome page opening doors is marketing prose that does not directly help tool invocation.

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?

For a zero-parameter read-only tool with no output schema, the description gives enough context: it names the membership tiers, says checkout links are returned, and describes the post-payment flow. The exact return shape is not specified, but the tool is simple enough that this is a minor 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 no parameters, so there are no parameter semantics to document. The baseline for a zero-parameter tool is 4, and nothing in the description undermines its usability.

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 identifies the resource clearly: RSMAD membership tiers, and states that it returns the tiers with Stripe checkout links. It is specific enough to distinguish this from generic artwork or space tools, though it does not explicitly contrast with get_offers.

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?

Usage is implied by the membership-tier and checkout-link framing, but there is no explicit when-to-use guidance or comparison to alternatives such as get_offers. An agent can infer that this is for retrieving membership purchase options, but must make that inference itself.

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