Skip to main content
Glama

purchase_persona

Generate a checkout URL on authority.md for purchasing one or more frameworks, Tools, Playbooks, or Bundles. Accepts 1-50 slugs (personas, Tools, and/or Playbooks, mixed carts allowed). To purchase a Bundle, pass all 10 of its persona slugs (get them from get_persona_details on the bundle slug: they will land on the $29.99 step-pricing tier automatically). Returns a URL the user follows to a checkout page hosted by authority.md that processes payment securely via Stripe. Personas use step pricing; Tools have individual prices; Playbooks are a flat $12.99 each. For current prices call get_persona_details per slug or read https://authority.md/products.json. Confirm with the user which items they want and the total cost BEFORE calling this tool.

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": {
      "slugs": "<slugs>"
    },
    "name": "purchase_persona"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that the tool returns a URL rather than charging anything itself, that payment is handled by Stripe on an authority.md-hosted page, and that mixed carts and step pricing apply. It stops short of stating URL lifetime/expiry, whether the call creates any server-side record, or rate limits, which are the remaining behavioral unknowns for a checkout-generation tool.

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-loaded with purpose, then cart rules, then the critical confirm-first instruction. It is dense but mostly earns its words; the step-pricing behavior is stated twice ('step-pricing tier automatically' and 'Personas use step pricing'), a minor redundancy in an otherwise efficient definition.

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 URL-returning purchase tool with no output schema, the description covers the return value, the payment flow, pricing models per item type, the Bundle edge case, and the human-confirmation prerequisite. Nothing essential to invoking it correctly appears to be missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and the only parameter is an untyped 'slugs' string array, so the description must compensate — and it does: it defines what a slug can be (persona, Tool, Playbook), states the 1-50 bound and that mixing is allowed, and gives the special Bundle rule of passing all 10 persona slugs. That is meaning well beyond the bare array schema.

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 artifact ('Generate a checkout URL on authority.md') plus the exact resource scope (frameworks, Tools, Playbooks, Bundles). This is clearly distinguishable from the read-only siblings get_persona_details, list_categories, and search_personas, which cannot produce a checkout flow.

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?

Explicitly instructs to confirm items and total cost with the user BEFORE calling, tells how to buy a Bundle (pass all 10 persona slugs fetched via get_persona_details), and routes pricing lookups to get_persona_details or products.json. The conditions that select this tool over the sibling reads are unambiguous.

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