Create a Stripe-hosted checkout link for one-time extra credits.
| Name | Required | Description | Default |
|---|---|---|---|
| pack_id | Yes | Credit pack to buy: pack_1000 or pack_10000. | |
| currency | No | Preferred checkout currency. | usd |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate openWorldHint=true and idempotentHint=false. The description adds useful context: it creates a Stripe-hosted checkout link for one-time credits, implying external payment processing. This goes beyond annotations without contradicting them.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence of 10 words. Every word is necessary and contributes to understanding the tool's purpose. No wasted verbiage.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description covers the core purpose adequately. Given the presence of a detailed input schema and output schema, the description need not elaborate further. Minor gap: it does not mention any prerequisites or that the returned link initiates a payment flow.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the schema already fully documents the parameters. The description does not add any additional meaning beyond what the schema provides, thus the baseline score of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the action ('Create'), the resource ('Stripe-hosted checkout link'), and the specific purpose ('for one-time extra credits'). This effectively distinguishes it from sibling tools like create_subscription_checkout and create_billing_portal_link.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides clear context by specifying 'one-time extra credits', which implies usage for credit purchases rather than subscriptions or billing management. However, it does not explicitly mention when not to use the tool or list alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose, covering different file operations (compress, convert, extract, merge, split, etc.) and billing management. No two tools overlap in functionality.
Most tool names follow a verb_noun pattern (compress_image, protect_pdf), but a few deviate (images_to_pdf, list_supported_conversions) causing minor inconsistency. The pattern is largely predictable.
17 tools is slightly above the typical well-scoped range, but still reasonable given the breadth of file manipulation and billing operations. Each tool serves a distinct need.
The file conversion and PDF manipulation operations are well-covered (compress, convert, extract, merge, split, protect, etc.). The billing tools are complete for subscription and credit management. Minor gaps exist, such as batch operations or image format conversions.