Skip to main content
Glama
Sign In

Framevine

by com.framevine
OverviewDiscussionsAdmin

Get credit purchase link

get_purchase_link

Get a Stripe Checkout link where the user can buy a credit pack. Nothing is charged by this tool: the user must open the link and pay on Stripe's page. Call without packId to list the available packs (packId, credits, price), then call again with the chosen packId.

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

Input Schema

NameRequiredDescriptionDefault
packIdNoCredit pack id from the pack list. Omit to list the packs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Goes beyond the annotations by clarifying that nothing is charged here and payment happens on Stripe's external page, which explains the openWorldHint=true and destructiveHint=false combo. It does not cover edge cases like invalid packId or link expiry, so it is strong but not exhaustive.

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?

Three short sentences, front-loaded with purpose, then the no-charge caveat, then the workflow. Every sentence carries distinct information with no filler.

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?

For a single optional-parameter tool with no output schema, the description supplies both the workflow and the shape of the pack list, so an agent can act correctly without further information.

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 packId description already says 'omit to list the packs,' so the description mostly repeats structured data. It does add the returned pack-list fields (packId, credits, price), which is marginally useful context.

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: returns a Stripe Checkout link for buying a credit pack. It also explicitly distinguishes its two modes (list packs vs. link for a chosen pack), which no sibling tool covers.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit two-step workflow: call without packId to list available packs, then call again with the chosen packId. Nothing is left to inference about when or how to sequence calls.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Framevine toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources