Skip to main content
Glama

Open billing checkout

billing_checkout

Create a Stripe checkout URL for a paid plan. Workspace owners only; return the URL to the user to finish in their browser.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "workspace_id": "<workspace_id>",
      "plan": "<plan>"
    },
    "name": "billing_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYes
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false and openWorldHint=true. The description adds genuinely useful context beyond that: an owner-only authorization gate and the fact that checkout must be completed by the user in a browser rather than in-process. It says nothing about what happens on repeat calls (each call likely mints a new session URL) or about error cases for invalid plans.

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?

Two short sentences, front-loaded with the action and followed by the constraint and the handoff instruction. Nothing redundant.

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 no output schema, the description correctly explains what is returned (a URL to hand to the user) and who may call it. For a two-parameter mutation-free checkout tool, that is close to sufficient; only repeat-call behavior and failure modes are unaddressed.

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 coverage is 50%: workspace_id is documented in-schema, while plan relies on an enum with no explanation. The description's 'paid plan' phrasing loosely frames the plan parameter and 'Workspace owners' frames workspace_id's scope, but it adds no real meaning beyond 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?

The description gives a specific verb and resource: 'Create a Stripe checkout URL for a paid plan.' This clearly separates it from management-type siblings like billing_portal or get_billing, though it never names an alternative explicitly.

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 states a hard precondition ('Workspace owners only') and the required follow-through ('return the URL to the user to finish in their browser'), which tells the agent this is a browser-handoff flow, not a server-side completion. It stops short of naming when to prefer billing_portal over checkout.

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