Skip to main content
Glama
Sign In
viridis-agent-fleet

viridis-agent-fleet

by jdhart81
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

subscriptions__create_checkout_link

Generate a Stripe Checkout URL for a subscription plan without charging a card. Validates plan readiness before creating the session.

Instructions

[subscriptions — B2B monthly seats, entitlement quota, overage, and MRR] Prepare a Stripe-hosted subscription Checkout URL. It never charges a card. Draft plans, missing owner approval, unavailable covered agents, or missing recurring Price IDs fail closed without creating a session.

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": {
      "plan_id": "<plan_id>",
      "account_ref": "<account_ref>"
    },
    "name": "subscriptions__create_checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
plan_idYes
account_refYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.1.11
    • addedInput schema / properties / account_ref / title
      Added value: +"Account Ref"
    • addedInput schema / properties / plan_id / title
      Added value: +"Plan Id"
    • addedInput schema / title
      Added value: +"create_checkout_linkArguments"
  2. Changed3 schema fields changedv0.1.9
    • removedInput schema / properties / account_ref / title
      Removed value: -"Account Ref"
    • removedInput schema / properties / plan_id / title
      Removed value: -"Plan Id"
    • removedInput schema / title
      Removed value: -"create_checkout_linkArguments"
  3. Added

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the tool never charges a card and fails closed under certain conditions, but lacks details on authentication, rate limits, or side effects. Moderate transparency.

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?

The description is two efficient sentences, front-loading the purpose with a bracketed context note. No redundant information.

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

Completeness3/5

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

For a simple tool with 2 parameters and no output schema, the description covers purpose and failure conditions but omits parameter semantics and return value details.

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 0% and the description does not explain the two required parameters (plan_id, account_ref) or their valid values. It mentions plan conditions but not parameter specifics.

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?

The description clearly states that the tool prepares a Stripe-hosted subscription Checkout URL, using specific verbs and resource identification. It also distinguishes itself from siblings by noting it never charges a card and listing failure conditions.

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

Usage Guidelines4/5

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

The description implicitly tells when to use (to prepare a checkout URL without charging) and lists failure conditions (draft plans, missing approval, etc.), but it does not explicitly compare to alternatives or give when-not-to-use guidance.

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

Deploy Server

Other Tools