Skip to main content
Glama

SaSame MCP Observatory + Gold Rush Town

by online.sasame
OverviewDiscussionsAdmin

factory_principal_register

Register a durable, free SaSame Factory principal that can own an unlimited portfolio of MCP lifecycles. No checkout, no charge. Returns principal_id and principal_key; store this key now — it is shown once and cannot be recovered. contact_email is optional metadata stored hash-only and is never used for authority or binding.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
display_refYesNon-secret human-readable reference for this principal
contact_emailNoOptional metadata; stored hash-only and never used as an authority or binding source
analytics_correlation_idNoOptional opaque journey token; only its SHA-256 hash is stored for cross-channel analytics.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / contact_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. Changed1 schema field changed
    • addedInput schema / properties / analytics_correlation_id
      Added value: +{
+  "description": "Optional opaque journey token; only its SHA-256 hash is stored for cross-channel analytics.",
+  "maxLength": 160,
+  "minLength": 8,
+  "pattern": "^[A-Za-z0-9._:-]+$",
+  "type": "string"
+}
  4. Added

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations, the description discloses critical behavior: it 'Returns principal_id and principal_key; store this key now — it is shown once and cannot be recovered.' It also clarifies contact_email is 'stored hash-only and is never used for authority or binding,' giving the agent important security and persistence context for a mutating operation.

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: the core purpose is in the first sentence, followed by short, high-value warnings about the one-time key and metadata handling. Every sentence earns its place, with no filler or repetition of schema details.

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?

With no output schema, the description appropriately explains the return values and the critical storage requirement. It also covers the optional metadata's privacy behavior. It could benefit from a note about whether calling again creates another principal, but the annotation idempotentHint=false already signals non-idempotence, so the missing detail is minor.

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 schema already documents all three parameters. The description reinforces contact_email's hash-only, non-authoritative semantics but adds little beyond what the schema states. This meets the baseline without adding substantial new parameter-level meaning.

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 ('Register') and resource ('durable, free SaSame Factory principal'), and clarifies it 'can own an unlimited portfolio of MCP lifecycles.' It also distinguishes itself from checkout flows by saying 'No checkout, no charge,' so an agent can tell this apart from sibling tools like factory_checkout.

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 gives clear context for when to use this tool: to create a principal without going through checkout or paying. It does not explicitly name alternatives or state when not to use it, but 'No checkout, no charge' effectively positions it against related lifecycle tools.

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