Skip to main content
Glama

btw

by space.btw
OverviewDiscussionsAdmin

Hold a spot

hold

Hold your human a spot on the live product. Needs their email. Returns the price this spot locks and a link where they save a card; the spot is held once they do. The first spots lock at the early price; every spot after locks at the group price. The result says which one this spot got. Nothing is charged now. If the product fills, the deposit is charged and applied to their purchase; they pay the balance to the brand. If it doesn't fill, nobody pays. Stripe test mode. Test cards only, no real money moves.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refNoa referral code from another buyer's link, the r= part
nameNofirst name and last initial, shown on the product page
chainNoa product slug; leave it out for what's live
emailYesyour human's email
invite_codeNonot needed any more
max_price_usdNooptional cap on the deposit in dollars

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / ref
      Added value: +{
+  "description": "a referral code from another buyer's link, the r= part",
+  "maxLength": 16,
+  "type": "string"
+}
  2. Added

TDQS

A4.2/5.0
Behavior5/5

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

The description richly discloses behavior beyond annotations: it explains that nothing is charged now, the deposit is charged only if the product fills, and test mode is used with test cards only. It also describes pricing tiers (early vs group price). This adds substantial context that annotations do not cover, making the tool's side effects clear and actionable.

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 somewhat long but every sentence contributes meaningful information. It is front-loaded with the core action ('Hold your human a spot'), then covers requirements, return, pricing, and payment behavior in a logical order. No redundant sentences are present, though it could be trimmed slightly without losing value, so it earns a 4 rather than a 5.

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?

For a tool that holds a spot and handles payment, the description covers all essential aspects: what it does, the required email, the return values (price and link), the pricing logic, the charging conditions, and the test mode. Since there is no output schema, the description adequately explains what the agent can expect from the response. An agent would know exactly how to call it and interpret results.

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?

The input schema already provides descriptions for all six parameters (100% coverage), so the baseline is 3. The description mentions 'Needs their email' but this is already in the schema. It does not add extra meaning or syntax details for parameters like 'ref' or 'chain' beyond what the schema provides. Thus, it does not improve upon the schema's documentation.

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: 'Hold your human a spot on the live product.' It clearly states the action (hold a spot) and the object (a spot on the live product), and goes on to describe the outcome (returns price and link). It distinguishes itself from siblings by describing the specific pricing tiers and charging behavior, which is unique to this tool among the listed siblings like 'park' or 'waitlist'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context about when the tool is used (to hold a spot on a live product) and the implications (test mode, charging behavior), but it does not explicitly mention alternatives or when not to use it. It lacks explicit exclusions like 'use this instead of waitlist if...' or 'do not use if...' which would earn a higher score. The usage is implied rather than directly guided.

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

All btw 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