Skip to main content
Glama

Hatch

by com.viberooster
OverviewDiscussionsAdmin

Create a payment link

checkout

Create a Stripe Checkout Session so the user can pay for a VibeRooster feature in this chat. Returns { checkoutUrl, sessionId, grant, amountCents } — ALWAYS show checkoutUrl to the user (open it / paste it). After they pay, call poll_checkout with sessionId until status is complete. The webhook applies the grant (Forever convert, coins, Agentic Pro, …). Do NOT call convert(newTier: forever) yourself.

Required ids by grant: publish / record / credit_topup → hatchId; workspace_coin_pack / workspace_subscription → workspaceId (or hatchId in that workspace); agentic_pro → orgId or workspaceId/hatchId attached to the org.

Do not use Stripe MCP (mcp.stripe.com) for VibeRooster features — that would charge a different Stripe account. Hatch checkout stamps hatch/workspace/org metadata the webhook expects.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
grantYes`publish` = Forever ($24.99 one-time). `workspace_coin_pack` = Continues. `agentic_pro` = enterprise HITL.
orgIdNoOrganization id. Required for Agentic Pro unless derivable from workspace/hatch.
hatchIdNoHatch id from hatch/lookup. Required for publish/record/credit_topup.
priceIdNoOptional Stripe Price id from `catalog`. Omit to use the mapped default for this grant.
quantityNoLine-item quantity (coin packs). Default 1.
tenantIdNoLegacy alias for `hatchId`.
workspaceIdNoWorkspace id. Required for coin packs and workspace subscription.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / hatchId
      Added value: +{
+  "description": "Hatch id from hatch/lookup. Required for publish/record/credit_topup.",
+  "type": "string"
+}
    • changedInput schema / properties / orgId / description
      Previous value: -"Organization id. Required for Agentic Pro unless derivable from workspace/tenant."New value: +"Organization id. Required for Agentic Pro unless derivable from workspace/hatch."
    • changedInput schema / properties / tenantId / description
      Previous value: -"Hatch id from hatch/lookup. Required for publish/record/credit_topup."New value: +"Legacy alias for `hatchId`."
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Beyond readOnly=false and openWorldHint=true, the description reveals the side-effectful flow: a Stripe session is created, the webhook later applies the grant, and the returned URL must be shown to the user. It also explains metadata stamping, which the annotations do not cover.

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?

Dense but front-loaded: the core action, return contract, and follow-up come first, with conditional id requirements and warnings after. Nearly every sentence earns its place, though the instructions could be tightened slightly.

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 7-parameter tool with no output schema, the description supplies return shape, post-payment polling protocol, cross-parameter id requirements, and integration cautions. Nothing needed to invoke it correctly is 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 100%, so the baseline is 3, but the description adds essential conditional logic absent from any single property: which id is required for each grant value (hatchId, workspaceId, orgId). It clarifies default priceId behavior and prevents incorrect cross-field choices.

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 the specific operation and resource: create a Stripe Checkout Session for a VibeRooster feature payment. It also differentiates from siblings by telling the agent to call poll_checkout afterward and not to call convert or the Stripe MCP.

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?

Gives explicit when-to-use and when-not-to-use instructions: show checkoutUrl, poll until complete, never call convert(newTier: forever), and never use Stripe MCP for VibeRooster. Also explains required ids per grant, so the agent knows prerequisites before calling.

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

All Hatch toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources