Cromanion

cromanion_upgrade_link

Get a Stripe Checkout link for a paid plan (pro or growth). Returns a URL and nothing else — YOU do not pay and cannot: give the link to your human, who enters their own card. The site works on the free plan meanwhile. Requires the claim secret as a bearer token.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`plan`	Yes	Which paid plan the link should check out: pro or growth. The site keeps working on free until your human completes it.
`siteId`	No	Which site this call is about. Only needed when your credential covers more than one — cromanion_grants lists them and says whether it is required. Omitting it with several is refused rather than guessed at.

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes
`plan`	Yes
`checkoutUrl`	Yes	A Stripe Checkout link. Give it to your human; you cannot complete it.
`instructions`	No	What to tell your human, in a sentence you can pass on unchanged.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed1 schema field changedSep 7, 2026

addedInput schema / properties / siteId

Added value: +{
+  "description": "Which site this call is about. Only needed when your credential covers more than one — cromanion_grants lists them and says whether it is required. Omitting it with several is refused rather than guessed at.",
+  "type": "string"
+}

Changed1 schema field changedSep 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "checkoutUrl": {
+      "description": "A Stripe Checkout link. Give it to your human; you cannot complete it.",
+      "type": "string"
+    },
+    "instructions": {
+      "description": "What to tell your human, in a sentence you can pass on unchanged.",
+      "type": "string"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "plan": {
+      "enum": [
+        "pro",
+        "growth"
+      ],
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "plan",
+    "checkoutUrl"
+  ],
+  "type": "object"
+}

Changed1 schema field changedSep 6, 2026

addedInput schema / properties / plan / description

Added value: +"Which paid plan the link should check out: pro or growth. The site keeps working on free until your human completes it."

First observedSep 6, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Beyond the annotations, the description discloses important behavior: it returns only a URL, it does not charge the AI, the human must enter their own card, the site remains on the free plan until checkout completes, and authentication requires a claim secret as a bearer token. This is substantial behavioral context that annotations alone do not provide.

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 compact and front-loaded with the tool's core purpose. Every sentence contributes: what it returns, who pays, what happens to the site during checkout, and the required auth. There is no filler or repetition of the schema.

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?

The tool is simple, has an output schema, and the description covers the two key operational facts an agent needs: the returned artifact is just a checkout URL, and auth is required via a bearer token. The schema covers plan and siteId semantics. Nothing necessary for correct invocation is missing.

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 description coverage is 100%, so the parameters are already well documented. The description adds little beyond what the schema provides; it mostly restates the plan options and the free-plan behavior already present in the schema. The baseline of 3 is appropriate because the description does not meaningfully compensate beyond the 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 resource: 'Get a Stripe Checkout link for a paid plan (pro or growth).' It also clarifies the exact output ('Returns a URL and nothing else'), making the tool's role unmistakable and distinguishable from siblings that manage goals, claims, or site status.

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 clearly indicates when to use the tool: when a paid plan upgrade link is needed and the human must complete checkout. It also gives an explicit guardrail — 'YOU do not pay and cannot: give the link to your human' — which is valuable usage guidance. It stops short of naming alternative tools or when not to use it, but the context is clear.

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

All Cromanion tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?