Skip to main content
Glama

SaSame MCP Observatory + Gold Rush Town

by online.sasame
OverviewDiscussionsAdmin

factory_checkout

Read-onlyIdempotent

Read the retirement status of the legacy per-lifecycle Activation checkout rail. New Activation sales are closed. Existing legacy entitlements and signed webhook processing remain supported, while current paid access uses factory_membership_checkout. This tool never creates a Checkout and never charges.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
buyer_emailNoDeprecated compatibility input; ignored and never persisted
lifecycle_idNoDeprecated compatibility input; ignored
lifecycle_keyNoDeprecated compatibility input; ignored and never persisted
stripe_live_payment_acknowledgedNoDeprecated compatibility field. factory_start never charges, and public Activation checkout creation is closed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / buyer_email / pattern
      Previous value: -"^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"New value: +"^(?:[A-Za-z0-9_'+\\-]+\\.)*[A-Za-z0-9_'+\\-]*[A-Za-z0-9_+-]@(?:[A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$"
  2. Changed1 schema field changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Changed5 schema fields changed
    • addedInput schema / properties / buyer_email / description
      Added value: +"Deprecated compatibility input; ignored and never persisted"
    • addedInput schema / properties / lifecycle_id / description
      Added value: +"Deprecated compatibility input; ignored"
    • addedInput schema / properties / lifecycle_key / description
      Added value: +"Deprecated compatibility input; ignored and never persisted"
    • changedInput schema / properties / stripe_live_payment_acknowledged / description
      Previous value: -"Required acknowledgement that completing the returned Checkout charges REAL money via Stripe LIVE mode at the owner-set activation price."New value: +"Deprecated compatibility field. factory_start never charges, and public Activation checkout creation is closed."
    • removedInput schema / required
      Removed value: -[
-  "lifecycle_id",
-  "lifecycle_key",
-  "buyer_email",
-  "stripe_live_payment_acknowledged"
-]
  4. Changed1 schema field changed
    • changedInput schema / properties / stripe_live_payment_acknowledged / description
      Previous value: -"Required acknowledgement that completing the returned Checkout charges REAL money via Stripe LIVE mode at the owner-set activation price. Reading tools never charges."New value: +"Required acknowledgement that completing the returned Checkout charges REAL money via Stripe LIVE mode at the owner-set activation price."
  5. Changed3 schema fields changed
    • addedInput schema / properties / stripe_live_payment_acknowledged
      Added value: +{
+  "const": true,
+  "description": "Required acknowledgement that completing the returned Checkout charges REAL money via Stripe LIVE mode at the owner-set activation price. Reading tools never charges.",
+  "type": "boolean"
+}
    • removedInput schema / properties / stripe_test_only_acknowledged
      Removed value: -{
-  "const": true,
-  "type": "boolean"
-}
    • changedInput schema / required
      Previous value: -[
-  "lifecycle_id",
-  "lifecycle_key",
-  "buyer_email",
-  "stripe_test_only_acknowledged"
-]New value: +[
+  "lifecycle_id",
+  "lifecycle_key",
+  "buyer_email",
+  "stripe_live_payment_acknowledged"
+]
  6. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context beyond that: it explicitly states the tool 'never creates a Checkout and never charges,' and clarifies that legacy entitlements/webhook processing still work. It does not describe return details, but this is minor for a status-read tool.

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 sentences with no filler. The core action and object are front-loaded, and each sentence contributes either scope, alternative routing, or a safety guarantee.

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?

For a read-only, no-required-params status tool, the description gives sufficient context: it identifies the legacy subject, names the current alternative, and reassures safety. It does not define the exact shape of 'retirement status,' but the calling pattern is simple and the schema covers input handling.

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%, with every parameter already marked as a deprecated/ignored compatibility input. The description adds no parameter-specific meaning beyond the schema, so the baseline of 3 applies.

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 states a specific verb and resource: 'Read the retirement status of the legacy per-lifecycle Activation checkout rail.' It clearly distinguishes from the sibling factory_membership_checkout by noting that current paid access uses that tool instead.

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?

It explicitly frames when this tool is relevant: new Activation sales are closed, existing legacy entitlements remain supported, and current paid access should use factory_membership_checkout. This gives an agent both a positive context (legacy status reads) and an exclusion (new/current paid flows).

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

All SaSame MCP Observatory + Gold Rush Town 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