Skip to main content
Glama

Boost codes

boost_code

Create a Stripe checkout to pin one or several of the user's codes (up to 12) to the top of their brand pages. Price per code depends on the brand category: standard 48h €0.79 / 1 week €1.49 / 3 weeks €2.99; telecom, energy, VPN, SaaS and insurance €0.99 / €1.79 / €3.49; finance and betting €1.19 / €2.29 / €3.99. Boosting several codes at once is discounted: 2 codes -10%, 3 codes -15%, 4 codes -20%, 5+ codes -30%. Returns a payment link the user must open to pay; the Boosts start as soon as payment succeeds.

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

Input Schema

NameRequiredDescriptionDefault
code_idNoSingle code id (same as code_ids with one item)
code_idsNoCode ids from list_my_codes; several codes get a volume discount
durationNoWEEK_1

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / code_id / description
      Previous value: -"Code id from list_my_codes"New value: +"Single code id (same as code_ids with one item)"
    • addedInput schema / properties / code_ids
      Added value: +{
      +  "description": "Code ids from list_my_codes; several codes get a volume discount",
      +  "items": {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  "maxItems": 12,
      +  "minItems": 1,
      +  "type": "array"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "code_id"
      -]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations say it's a non-readonly, open-world, non-idempotent, non-destructive mutation. The description adds crucial behavior: it returns a payment link the user must open, boosts only start after successful payment, and volume discounts apply. That is exactly the behavioral context an agent needs beyond the annotations.

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?

It is front-loaded with the primary action and follows with pricing/discount context that is genuinely useful for estimating cost. The pricing tier sentence is dense and lengthy, but it earns its place by giving concrete costs the agent may need to relay to the user.

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

Completeness5/5

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

Given three parameters, no output schema, and non-trivial payment behavior, the description covers the key gaps: what it creates, what it returns, how payment works, pricing, and discount rules. It is complete enough for an agent to call the tool and explain the outcome to the user.

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 coverage is 67%, and the description compensates by explaining that several codes trigger discounts and that the price depends on the brand category and chosen duration, which maps to code_ids and duration. It doesn't explicitly explain the code_id vs code_ids alias, but that is already covered by the schema description.

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 opens with a specific verb and resource: 'Create a Stripe checkout to pin one or several of the user's codes ... to the top of their brand pages.' It clearly distinguishes from siblings like list_my_codes and publish_code by naming the exact paid promotion action and its outcome.

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?

The description makes it clear when to use this: when a user wants to pin/boost codes, including price tiers to help the agent confirm costs and a note that codes come from the user's own list. No explicit exclusions or named alternatives, but the preconditions ('user's codes', 'up to 12', payment required) are stated.

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