SavedThat

Show SavedThat plans

show_plans

Show SavedThat's paid plans (Pro and Power, monthly or yearly) with current prices and a checkout or billing-portal link for each, rendered as an interactive card. Use it when the user asks about pricing or plans, wants to change plan, or has reached a plan limit. The returned text carries the links the user needs to act on.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`note`	No
`plans`	Yes
`channel`	Yes
`currency`	No
`manageUrl`	No
`currentPlan`	Yes
`yearlySavingsPct`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Beyond the annotations it discloses that the tool returns an interactive card containing actionable checkout or billing-portal links, which tells the agent what the user can do with the result. It does not explain why readOnlyHint=false (likely an external billing/checkout session being created), so the non-read-only annotation remains unexplained — a real but modest gap.

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

Conciseness5/5

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

Three sentences, front-loaded with what the tool returns and followed by when to call it and what the user gets out of it. No filler, no repetition of the title.

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 an output schema present and no inputs, the description only needs to carry purpose, triggers, and actionability, all of which it covers. The single missing piece is a note on the non-read-only nature implied by the annotations.

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?

Zero parameters, so there is nothing to disambiguate; the baseline applies. The description correctly does not waste space restating an empty schema.

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?

The description names a specific verb and resource ('Show SavedThat's paid plans'), enumerates the exact content (Pro and Power, monthly or yearly, current prices, checkout/billing-portal links), and states the render form ('interactive card'). No sibling tool touches billing or plans, so the agent can distinguish it immediately.

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

Usage Guidelines5/5

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

It gives three concrete invocation triggers: user asks about pricing/plans, user wants to change plan, or a plan limit has been reached. With no competing sibling in this domain, explicit exclusions are unnecessary and the guidance is complete for selection purposes.

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

All SavedThat tools Inspect

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.