Skip to main content
Glama

btw

by space.btw
OverviewDiscussionsAdmin

Hold a spot (old name)

join

The old name for 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. Changed7 schema fields changed
    • changedInput schema / properties / chain / description
      Previous value: -"chain slug from list_chains"New value: +"a product slug; leave it out for what's live"
    • removedInput schema / properties / chain / minLength
      Removed value: -1
    • changedInput schema / properties / invite_code / description
      Previous value: -"the friends invite code"New value: +"not needed any more"
    • removedInput schema / properties / invite_code / minLength
      Removed value: -1
    • changedInput schema / properties / max_price_usd / description
      Previous value: -"the most your human would pay, in dollars"New value: +"optional cap on the deposit in dollars"
    • changedInput schema / properties / name / description
      Previous value: -"first name and last initial, for the public chain page"New value: +"first name and last initial, shown on the product page"
    • changedInput schema / required
      Previous value: -[
-  "chain",
-  "max_price_usd",
-  "email",
-  "invite_code"
-]New value: +[
+  "email"
+]
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

The description discloses substantial behavioral detail beyond annotations: no charge happens immediately, a link is returned, pricing tiers differ based on spot order, conditional deposit charging occurs only if the product fills, and Stripe test mode is used with test cards only. This lets the agent understand the real-world effects of invocation.

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 carries relevant operational information: pricing, return value, charge behavior, and test-mode limitation. It is front-loaded with the alias relationship and tool purpose. Minor awkward phrasing like 'your human a spot' prevents a perfect conciseness score.

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 tool with no output schema, the description explains the return contents (price, link, tier), the pricing rule, and the charge lifecycle, which gives an agent enough to invoke it and interpret results. It could be more complete by explicitly stating the deprecation policy and directing callers to the 'hold' tool, but the 'old name' mention partially covers this.

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 schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds only that email is required, which is already in the schema as a required field. It does not meaningfully augment parameter-level meaning beyond the schema.

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 clearly identifies the tool as 'the old name for hold' and states its action: holding a spot for a human on the live product. This explicitly links it to the sibling tool 'hold' and distinguishes it from unrelated siblings like join_chain 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 gives clear context that this is a deprecated alias for hold and mentions the email prerequisite, but it does not explicitly say when to choose this tool over hold or provide exclusions for other alternatives. Usage guidance is implied rather than direct.

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