Create a Stripe-hosted checkout link for a Pro or Scale subscription.
| Name | Required | Description | Default |
|---|---|---|---|
| annual | No | Use annual billing instead of monthly. | |
| plan_id | Yes | Plan to subscribe to: pro or scale. | |
| 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 indicate openWorldHint=true and idempotentHint=false, so the description correctly implies an external side effect (creating a Stripe Checkout Session). However, it does not explicitly mention that calling the tool multiple times creates multiple checkouts (non-idempotent) or that it interacts with Stripe's API, which would be helpful for an agent.
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, clear sentence with no unnecessary words. It is front-loaded and efficiently conveys the tool's purpose.
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?
Given the tool is simple with 3 fully described parameters and an output schema, the description is mostly complete. It could mention that the returned value is a checkout link, but the output schema covers that. Minor gap for a straightforward tool.
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 coverage is 100%, so the input schema already fully describes the parameters. The description adds no extra meaning beyond saying 'Pro or Scale subscription', which aligns with plan_id enum. This is adequate but not additive.
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 tool's function: 'Create a Stripe-hosted checkout link for a Pro or Scale subscription.' The verb 'Create' and resource 'checkout link' are specific, and the mention of 'Pro or Scale' distinguishes it from sibling tools like create_credit_pack_checkout or 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 implies usage for subscription checkout but provides no explicit when-to-use or when-not-to-use guidance, nor references to alternatives like create_billing_portal_link for managing existing billing or create_credit_pack_checkout for credit packs.
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.