Skip to main content
Glama

buy_auto_apply_credits

Destructive

Create a Stripe Checkout link for Auto Apply credits: plan "pack" = 50 applications, "unlimited" = 30 days of unlimited applications. The user opens the link and pays; once paid, the credits show up in get_account. Uses the user's minutes or credits or creates a payment; tell the user what it costs and get their agreement first. (Requires the user's sign-in with scope account:write.)

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": {
      "plan": "<plan>"
    },
    "name": "buy_auto_apply_credits"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYespack = 50 applications; unlimited = 30 days unlimited

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already flag destructiveHint=true and readOnly=false, and the description adds real context beyond them: the charge may draw on minutes or credits or create a payment, and the resulting credits appear in get_account. It omits link expiry, idempotency, and what happens if the user abandons checkout.

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?

Front-loads the action and plan semantics, then the consent requirement and auth scope. Dense but every clause carries information; the parenthetical auth note is slightly tacked on.

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 still conveys the return (a checkout link the user opens) and the post-condition (credits visible in get_account), plus the auth requirement. Enough for an agent to call it correctly, though 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 100% and the enum already documents both plan values, so the description's restatement of "pack = 50 applications" and "unlimited = 30 days" adds no meaning beyond the schema. Baseline 3 applies.

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?

States a specific verb and resource ("Create a Stripe Checkout link for Auto Apply credits") and immediately defines the two plan values, so an agent can distinguish this purchase flow from siblings like get_auto_apply_quota or redeem_credits.

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?

Gives a clear operating condition: tell the user the cost and get agreement before invoking, and notes the required account:write sign-in scope. It does not explicitly contrast with redeem_credits or get_auto_apply_quota, so the when-not guidance is incomplete.

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