Skip to main content
Glama

SOMA Non-Alcoholic Craft Beer

Get a checkout link for a SOMA order

get_buy_link
Read-only

Builds a direct buy link an agent can hand to the user. IMPORTANT: every order placed today is a PRE-ORDER. Production starts in December 2026; shipping follows later, with no confirmed dispatch date. 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.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "get_buy_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesBeer slug: lager, ipa, belgian-wit, stout, stout-caffeinated
formatNoPurchase format: bottle200 = single 200ml bottle, sixPackBottle200 = 6 × 200ml bottles; smallCan = single 250ml can, sixPackSmallCan = 6 × 250ml cans; bottle330 = single 330ml bottle, sixPackBottle330 = 6 × 330ml bottles; can = single 500ml can, sixPack = 6 × 500ml canscan
quantityNoHow many units

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing output variance (Shopify cart permalink when variant IDs are configured, otherwise the product page), that payment occurs on Shopify's checkout, and that the tool never charges anyone. It also flags the time-sensitive pre-order status with a December 2026 production start and no confirmed dispatch date.

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?

Four short sentences, front-loaded with what the tool produces, followed by the mandatory pre-order disclosure and then output/payment behavior. No redundant wording; each sentence carries distinct information.

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 correctly compensates by explaining the two return shapes and where the transaction occurs. For a three-parameter read-only link builder, nothing material 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% and both enum parameters plus quantity are fully documented in the schema, including format meanings and the 1–48 quantity bound. The description adds no further parameter semantics, 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?

States a specific verb and artifact ('Builds a direct buy link') and who it is for ('an agent can hand to the user'). It also clarifies the two possible outputs (cart permalink vs. product page), which distinguishes it from catalog tools like get_beer or list_beers that do not produce a checkout path.

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?

Gives clear usage context: the link is meant to be handed to the user, and the pre-order caveat must be surfaced alongside it. It does not explicitly name sibling alternatives or state when-not to use this tool (e.g., for wholesale or subscription questions), so guidance is clear but not complete.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources