Skip to main content
Glama

Get Onboarding Plan Options

get_onboarding_plan_options
Read-only

Get complete live Pro and Platinum benefits, prices, billing cycles, fees, trials, and discounts. Display only PRO and PLATINUM monthly or yearly options, ask the user to select a plan type and period, and carry the returned priceId unchanged.

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

Input Schema

NameRequiredDescriptionDefault
discountCodeNo
referralCodeNoReferral code to look up.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / referralCode / description
      Added value: +"Referral code to look up."
  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, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds meaningful context beyond that: the data is 'live', it comes back with a priceId that must be passed downstream unchanged, and the agent is expected to present a filtered option set to the user. It does not describe error behavior when codes are invalid or whether results are paginated.

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 dense sentences with no filler, and the capability statement is front-loaded before the presentation/selection instructions. The list of returned data fields is long but each item earns its place by telling the agent what to surface. Minor awkwardness from packing instructions into a single run-on sentence.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

It is a read-only two-parameter tool with no output schema, so the description must carry the return shape – and it does reasonably well by enumerating benefits, prices, billing cycles, fees, trials, discounts, and priceId. However, it says nothing about how the two code parameters alter results or what happens when no options match. Adequate but not fully complete for a pricing tool.

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?

With two optional parameters and 50% schema description coverage, the schema only documents referralCode; discountCode is left bare. The description mentions 'discounts' in the returned data but never explains what discountCode does, how it differs from referralCode, or how either affects the returned prices. That is a 3 baseline – adequate, with a clear gap on the undocumented parameter.

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 gives a concrete verb ('Get') and enumerates the resource contents: live Pro and Platinum benefits, prices, billing cycles, fees, trials, and discounts. That is far more specific than the bare name, and the Pro/Platinum plus onboarding framing distinguishes it from generic plan tools like get_plan_info. It stops short of explicitly naming which sibling to use for other plan tiers or for non-onboarding price lookups.

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 real workflow direction: display only PRO and PLATINUM monthly or yearly options, ask the user to pick a plan type and period, then carry the returned priceId unchanged. That is clear when-to-use and how-to-present guidance. It does not state when not to use it or name an alternative for other tiers, so it falls 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources