Skip to main content
Glama
Sign In

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 (Pin, Pack, Roost, Roost Audit, custom domain).

Required ids by grant: publish / record / credit_topup / workspace_coin_pack (Pack) → hatchId; workspace_subscription (Roost) / custom_domain → workspaceId (or hatchId in that workspace); agentic_pro (Roost Audit) → 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

NameRequiredDescriptionDefault
grantYes`publish` = Pin ($4.99/yr, 1-year keep; also overage after 10 subscription Pins). `workspace_subscription` = Roost ($259/mo). `agentic_pro` = Roost Audit ($459/mo). `workspace_coin_pack` = Pack ($4.99/yr per GB). `custom_domain` = +$29/mo on Roost / Roost Audit.
orgIdNoOrganization id. Required for Roost Audit (`agentic_pro`) unless derivable from workspace/hatch.
hatchIdNoHatch id from hatch/lookup. Required for publish (Pin), record, credit_topup, and Pack.
priceIdNoOptional Stripe Price id from `catalog`. Omit to use the mapped default for this grant.
quantityNoLine-item quantity (Pack GB, custom domain slots). Default 1.
tenantIdNoLegacy alias for `hatchId`.
workspaceIdNoWorkspace id. Required for Roost (`workspace_subscription`) and custom_domain.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / grant / description
      Previous value: -"`publish` = Forever ($24.99 one-time). `workspace_coin_pack` = Continues. `agentic_pro` = enterprise HITL."New value: +"`publish` = Pin ($4.99/yr, 1-year keep; also overage after 10 subscription Pins). `workspace_subscription` = Roost ($259/mo). `agentic_pro` = Roost Audit ($459/mo). `workspace_coin_pack` = Pack ($4.99/yr per GB). `custom_domain` = +$29/mo on Roost / Roost Audit."
    • changedInput schema / properties / grant / enum
      Previous value: -[
-  "publish",
-  "record",
-  "credit_topup",
-  "workspace_coin_pack",
-  "workspace_subscription",
-  "agentic_pro"
-]New value: +[
+  "publish",
+  "record",
+  "credit_topup",
+  "workspace_coin_pack",
+  "workspace_subscription",
+  "agentic_pro",
+  "custom_domain"
+]
    • changedInput schema / properties / hatchId / description
      Previous value: -"Hatch id from hatch/lookup. Required for publish/record/credit_topup."New value: +"Hatch id from hatch/lookup. Required for publish (Pin), record, credit_topup, and Pack."
    • changedInput schema / properties / orgId / description
      Previous value: -"Organization id. Required for Agentic Pro unless derivable from workspace/hatch."New value: +"Organization id. Required for Roost Audit (`agentic_pro`) unless derivable from workspace/hatch."
    • changedInput schema / properties / quantity / description
      Previous value: -"Line-item quantity (coin packs). Default 1."New value: +"Line-item quantity (Pack GB, custom domain slots). Default 1."
    • changedInput schema / properties / workspaceId / description
      Previous value: -"Workspace id. Required for coin packs and workspace subscription."New value: +"Workspace id. Required for Roost (`workspace_subscription`) and custom_domain."
  2. 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`."
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses the webhook side effect (grant applied), the exact return shape, the required follow-up polling behavior, and the metadata stamping the webhook expects. This gives the agent a clear model of what the call starts and what happens afterward.

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?

The description is long, but every block earns its place: behavior, return value, follow-up, required-id mapping, and the Stripe MCP warning. Essential call semantics are front-loaded; the grant-specific detail is dense but necessary for correct invocation.

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?

With no output schema, the description fully compensates by specifying the return shape, post-payment actions, grant-specific id requirements, and default pricing behavior. The agent has everything needed to invoke checkout correctly and continue the flow.

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

Parameters4/5

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

Schema coverage is 100%, but the description adds important conditional semantics: required ids by grant, default behavior when priceId is omitted, and quantity meaning per grant. This adds real value beyond the schema's per-field descriptions, though the schema already documents each field.

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 opens with a specific verb and resource: 'Create a Stripe Checkout Session so the user can pay for a VibeRooster feature in this chat.' This clearly distinguishes checkout from sibling tools like poll_checkout and catalog by stating its exact role in the payment flow.

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?

The description gives explicit when-to-use guidance: create the checkout session, ALWAYS show checkoutUrl, then poll_checkout until status is complete. It also names an explicit exclusion: do not use Stripe MCP for VibeRooster features, which steers the agent away from a plausible wrong tool.

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
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources