Skip to main content
Glama

plans

Read-onlyIdempotent

The Cubicle plans (price per 30 days, what each includes) and exactly how to pay on Robinhood Chain in USDG: the treasury, the token, and — when the subscription vault is live — the two wallet transactions (approve, subscribe) that renew automatically every 30 days. Nothing here moves money: the trader signs in their own wallet.

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": "plans"
  }
}

Input Schema

NameRequiredDescriptionDefault
planNoa plan id (starter-20, pro-50 or premium-99) to prepare the payment steps for
walletNothe 0x address of the wallet that will pay — needed for the renewing subscription, which is authorized for that wallet only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / plan / description
      Previous value: -"a plan id (pro-50 or premium-99) to prepare the payment steps for"New value: +"a plan id (starter-20, pro-50 or premium-99) to prepare the payment steps for"
    • changedInput schema / properties / plan / enum
      Previous value: -[
      -  "pro-50",
      -  "premium-99"
      -]New value: +[
      +  "starter-20",
      +  "pro-50",
      +  "premium-99"
      +]
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds substantive context beyond them: 'Nothing here moves money: the trader signs in their own wallet', and it discloses that the subscription vault may not yet be live, in which case the approve/subscribe steps are absent. It also states the renewal cadence (every 30 days). Remaining gaps are minor — no mention of response shape or caching.

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 payoff (plans and prices) before the payment mechanics, and the safety claim is placed last for emphasis. The middle clause is dense and dash-heavy but every element — treasury, token, approve/subscribe, 30-day renewal — carries information.

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?

For a read-only informational tool with no output schema, the description covers what is returned, the conditional case (vault not live), the renewal semantics, and the no-funds-moved guarantee. An agent has everything needed to call it and interpret the result correctly.

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 description coverage is 100% and both parameters are already documented, including the enum ids and the fact that wallet is only needed for the renewing subscription authorized to that wallet. The description adds framing ('prepare the payment steps') but no new parameter-level detail such as what happens when wallet is omitted. Baseline 3 applies.

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 the resource concretely — Cubicle plans with price per 30 days and inclusions, plus the payment path on Robinhood Chain in USDG (treasury, token, approve/subscribe transactions). That is far more than a restatement of the name 'plans'. It does not, however, explicitly differentiate itself from siblings like price, catalogue, or plan_claim, so an agent must infer the boundary.

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 rather than stated: you read this to learn pricing and 'exactly how to pay', and the schema note says the plan param prepares payment steps. There is no explicit when-to-use/when-not-to-use rule and no named alternative (e.g. plan_claim for actually claiming), which is the main gap for a tool with an obvious transactional sibling.

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