Skip to main content
Glama

Subscribe to Premium

subscribe_premium

Create a Stripe checkout for Koddeo Premium (auto-refresh: the user's codes move back up whenever another code of the same brand is refreshed, published or boosted; Premium badge): €9.99/month or €95.88/year. Returns a link the user must open to pay. If already subscribed, returns the billing portal.

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

Input Schema

NameRequiredDescriptionDefault
planNoYEARLY

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, openWorldHint=true and idempotentHint=false, and the description adds real behavioral context beyond them: the call yields a URL the user must open, and an already-subscribed user instead gets a billing-portal link. It does not warn that repeated calls (non-idempotent) can spawn multiple Stripe checkout sessions, which would be the remaining useful disclosure.

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?

The core action is front-loaded in the first clause, and every later clause (benefits, price, return link, subscribed fallback) carries operational value. The long parenthetical listing auto-refresh mechanics is somewhat marketing-heavy and makes the single sentence dense, but nothing is truly wasted.

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 one-parameter, non-destructive, open-world tool with no output schema, the description covers the key agent decisions: what is created, what the user must do next, cost per plan, and the subscribed-user fallback path. Only authentication/account prerequisites and the non-idempotency risk are absent.

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?

Schema description coverage is 0% and the only parameter is a MONTHLY/YEARLY enum, but the description supplies the meaning of each option through pricing (€9.99/month vs €95.88/year), which is the decision-relevant information for that parameter. It never names the parameter or mentions the YEARLY default, so it complements rather than substitutes for the schema.

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?

States a specific verb and object — 'Create a Stripe checkout for Koddeo Premium' — plus the price points and what Premium buys, so the agent knows exactly what action this performs. It does not explicitly differentiate from paid siblings such as boost_code, even though boosting is mentioned inside the benefits parenthetical, leaving a small ambiguity about subscription vs. per-code boost.

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?

'Returns a link the user must open to pay' tells the agent the flow does not complete payment, and 'If already subscribed, returns the billing portal' handles the main pre-existing-state case. There is no explicit guidance on choosing this over boost_code or on account prerequisites, so context is clear but alternatives are not named.

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