Skip to main content
Glama
Sign In

btw

by space.btw
OverviewDiscussionsAdmin

Want a gym or studio membership

want_gym
Idempotent

Your human wants a membership at a gym or studio near them. Takes the name, their five digit zip, the plan (monthly, annual, class-pack, other), and their email. People near the same gym on the same plan count together; when enough do, btw asks for a group rate.

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": {
      "name": "<name>",
      "zip": "<zip>",
      "plan": "<plan>",
      "email": "<email>"
    },
    "name": "want_gym"
  }
}

Input Schema

NameRequiredDescriptionDefault
zipYesfive digit US zip
nameYesgym or studio name
planYesthe plan
emailYesyour human's email, same as the waitlist

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.4/5.0
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it explains the aggregation mechanism ('People near the same gym on the same plan count together') and the side effect ('when enough do, btw asks for a group rate'). This is valuable behavior disclosure that annotations (readOnlyHint false, idempotentHint true) do not cover. No contradiction.

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 two concise sentences that front-load the purpose, then list the parameters, then state the behavioral nuance. There is no filler or redundancy; every clause contributes to understanding.

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 4 simple parameters, no output schema, and clear annotations, the description covers purpose, parameters, and the key aggregation behavior. It could optionally mention what happens after the want is recorded, but that is likely covered by the overall btw flow. Overall it is complete enough for an agent to call it correctly.

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 the description essentially restates the parameters (name, five-digit zip, plan enum, email). It adds no new meaning beyond what the schema already provides, such as format, constraints, or purpose. The baseline of 3 is appropriate since the schema carries the semantic load.

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 states the tool records a desire for a gym or studio membership: 'Your human wants a membership at a gym or studio near them.' It names the specific resource type and lists the key parameters, making it easily distinguishable from siblings like want_home, want_software, and want_stay.

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 makes it obvious when to use this tool: whenever the want is for a gym or studio. It does not explicitly mention alternatives, but the contrast with sibling tools is implicitly clear from the specific resource type. No exclusions or competing conditions are stated, but the scope is unambiguous.

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