Skip to main content
Glama

create_stripe_checkout

Create a Stripe Checkout for a HOBO Works product at its published fixed price. No marketplace commission.

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": {
      "product_id": "<product_id>"
    },
    "name": "create_stripe_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
product_idYes
owner_briefNoFor a service: the owner's goal, supplied inputs, constraints, and expected deliverable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / owner_brief
      Added value: +{
      +  "description": "For a service: the owner's goal, supplied inputs, constraints, and expected deliverable.",
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden. It does add useful economics ('published fixed price', 'no marketplace commission'), but says nothing about what the call actually creates (a session? a URL?), whether it's an external side effect, how long the checkout lives, or what permissions matter.

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?

A single tight sentence with the distinguishing detail (Stripe, fixed price, no commission) front-loaded. Nothing is wasted, though the brevity is partly the source of the coverage gaps.

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

Completeness2/5

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

This is a side-effectful payment tool with no annotations, no output schema, and one undocumented parameter — the description should do far more. Missing are the return shape (checkout URL/session id), the fact that owner_brief is expected for services, and routing against the crypto and rental checkout siblings.

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

Parameters2/5

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

Schema coverage is only 50%: owner_brief is documented in the schema, but product_id has no description anywhere. The description never mentions either parameter, so it fails to compensate — notably it omits that owner_brief is the mechanism for service products, which is the one genuinely non-obvious input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Create') and resource ('Stripe Checkout for a HOBO Works product'), plus the pricing rule (published fixed price). The word 'Stripe' implicitly distinguishes it from create_crypto_invoice and create_rental_checkout, but neither sibling is named, so the differentiation is left to inference.

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

Usage Guidelines2/5

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

There is no guidance on when to choose this over create_crypto_invoice or create_rental_checkout, which are directly parallel alternatives in the sibling list. No prerequisites are stated either — nothing about buyer identity, product state, or when a checkout is inappropriate.

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