Skip to main content
Glama

SOMA Brewing Company

by store.getsoma
OverviewDiscussionsAdmin

Get a checkout link for a SOMA order

get_buy_link

Builds a direct buy link an agent can hand to the user. IMPORTANT: SOMA is not in production yet — every order placed today is a PRE-ORDER, production starts after December 2026, and nothing ships before then. Say so when you surface this link. With Shopify variant IDs configured it returns a cart permalink that lands in checkout pre-filled; otherwise it returns the product page on the shop. Payment always happens on Shopify's checkout with the human in control — this tool never charges anyone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesBeer slug: lager, ipa, belgian-wit, stout, stout-caffeinated
formatNoPurchase format: smallCan = single 250ml can, can = single 500ml can, sixPack = 6 × 500ml canscan
quantityNoHow many units

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / slug / description
      Previous value: -"Beer slug: lager, ipa, belgian-wit, or stout"New value: +"Beer slug: lager, ipa, belgian-wit, stout, stout-caffeinated"
  2. Changed2 schema fields changed
    • changedInput schema / properties / format / description
      Previous value: -"Purchase format: single 500ml can or a 6-pack of cans"New value: +"Purchase format: smallCan = single 250ml can, can = single 500ml can, sixPack = 6 × 500ml cans"
    • changedInput schema / properties / format / enum
      Previous value: -[
-  "can",
-  "sixPack"
-]New value: +[
+  "smallCan",
+  "can",
+  "sixPack"
+]
  3. Changed1 schema field changed
    • changedInput schema / properties / slug / enum
      Previous value: -[
-  "lager",
-  "ipa",
-  "belgian-wit",
-  "stout"
-]New value: +[
+  "lager",
+  "ipa",
+  "belgian-wit",
+  "stout",
+  "stout-caffeinated"
+]
  4. First observed

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden—and it delivers. It discloses the pre-order status, shipping timeline, the two possible return behaviors (cart permalink vs. product page), and that the tool never charges anyone. This is exemplary transparency for a side-effecting purchase 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?

The description is appropriately sized and front-loaded with the most important fact ('Builds a direct buy link'), followed by the critical pre-order caveat. Every sentence earns its place; the length is justified by the operational warnings and return-behavior distinctions.

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?

Despite having no output schema, the description fully explains what the agent can expect: a cart permalink if variant IDs are configured, otherwise a product page. It also covers the important user-facing caveats and payment model. Nothing essential for correctly invoking and presenting this tool 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 baseline is 3. The description adds useful behavioral context about 'pre-filled checkout' and variant IDs, but it doesn't explain the input parameters themselves beyond what the schema already documents. The schema handles parameter semantics adequately.

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 uses a specific verb ('Builds') and a clear resource ('direct buy link an agent can hand to the user'). It clearly distinguishes this tool from the sibling get_* tools by focusing on the checkout/purchase-link action, so an agent can select it without ambiguity.

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 the tool and even instructs the agent to disclose the pre-order status. It does not explicitly name alternative tools or when-not-to-use conditions, but the use case is specific enough that this is a minor gap rather than a fatal one.

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

All SOMA Brewing Company 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