Skip to main content
Glama

Vigil Website MCP

create_checkout

Start a purchase of one offer. Returns a continue_url: send the buyer there to pay on the Stripe-hosted checkout page. This tool does not charge anything.

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": {
      "offer_id": "<offer_id>"
    },
    "name": "create_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
offer_idYes
quantityNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the bar is lower, yet the description still adds real value: it discloses that the return value is a continue_url the caller must hand to the buyer, that payment happens on a Stripe-hosted page, and that this call itself performs no charge. It omits that each call presumably opens a new external session and any session-expiry behavior, but the core behavioral picture is solid.

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 the action and immediately followed by what to do with the result and what the tool does not do. Every sentence earns its place with no filler.

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

Completeness4/5

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

With no output schema, the description correctly compensates by explaining the return value (continue_url) and the follow-up action required. For a two-parameter, non-destructive creation tool this is nearly sufficient; the remaining gap is the undocumented quantity parameter.

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 description coverage is 0% for two parameters, so the description carries the full burden and largely does not: 'one offer' hints that offer_id is a single selection rather than a list, but the enum values are never explained and quantity (range 1-20, default 1) is never mentioned at all.

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?

Names a specific verb and resource ('Start a purchase of one offer') and states the immediate outcome (a continue_url pointing at a Stripe-hosted page). It is clear what the tool does, but it never distinguishes itself from the sibling get_checkout, leaving the create-vs-retrieve split 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 Guidelines3/5

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

The description implies usage ('send the buyer there to pay') and clarifies that the payment step happens elsewhere, which is useful routing guidance. However, it never states when to call this versus get_checkout or list_products, and gives no preconditions such as whether an existing checkout session can be reused.

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