Skip to main content
Glama

Strong Saga Home Gym Gear Finder

Build my home gym (full kit)

build_my_home_gym
Read-only

Use when a user asks "build my home gym", "what should I buy for my garage gym with $1,500" or "full home gym for a spare room with a 7.5 ft ceiling". Give the total budget in USD and describe the space in plain words (garage, basement, spare room or apartment, ceiling height, square feet or width x length). Returns a full kit: rack, barbell, plates, bench and rubber flooring, plus adjustable dumbbells and a landmine when money is left, each chosen only from products and prices in published Strong Saga guides and checked against the ceiling and floor. Each item has its guide_url (link the user there for current prices and buy buttons), price, quantity and cost; the answer gives the total at guide prices. If the budget cannot cover a full kit, budget_too_low is true, missing names what is left out and lowest_full_kit_usd says what a full kit starts at. With no budget it answers with the required and optional fields and the budget guide picks instead of an error; a budget in words ("about $1,500") is read as a number.

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": {
      "budget": "<budget>"
    },
    "name": "build_my_home_gym"
  }
}

Input Schema

NameRequiredDescriptionDefault
spaceNoThe space in plain words: type (garage, basement, spare room, apartment), ceiling height and size, e.g. "garage, 8 ft ceiling, 10x12 ft" or "spare room, 7 ft 6 in ceiling, 90 sq ft".
sq_ftNoFree floor area in square feet, if not given in space.
budgetYesTotal USD for the whole kit, e.g. 1500.
floor_ftNoFree floor area as width x length in feet, e.g. 10x12, if not given in space.
ceiling_inNoCeiling height in inches (8 ft = 96), if not given in space.
user_height_inNoUser height in inches, for pull-up clearance under the ceiling.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only declare readOnlyHint and openWorldHint=false; the description adds substantial behavior: items are drawn solely from published Strong Saga guides, checked against ceiling height and floor area, and priced at guide prices via guide_url. It also discloses the degraded path (budget_too_low, missing, lowest_full_kit_usd) and that a missing budget returns field guidance rather than an error, which is exactly the kind of non-obvious behavior an agent needs.

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?

Trigger conditions are front-loaded in the first clause, followed by input requirements, output shape, and fallbacks in a logical order. It is dense but nearly every clause carries information; however, the middle sections run together as one long paragraph, making the return-shape and edge-case rules harder to scan than they need to be.

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 carries the full burden of explaining returns, and it does: per-item guide_url, price, quantity and cost, plus the total and the budget_too_low / missing / lowest_full_kit_usd fields. A minor inconsistency is that budget is marked required in the schema while the description describes a no-budget path, but the behavior is at least stated rather than left ambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, and the description still adds real meaning: budget is stated as total USD for the whole kit, space should be described in plain words, and notably that a budget in words ("about $1,500") is parsed as a number. That parsing leniency is not visible in the schema and changes how an agent should populate the field.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (build a full home gym kit) and enumerates the exact contents: rack, barbell, plates, bench, rubber flooring, plus dumbbells and landmine when budget allows. It does not differentiate itself from the sibling tool build_home_gym, which from the name alone looks nearly identical, so an agent cannot disambiguate those two from this text.

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?

Opens with explicit trigger phrases ("build my home gym", "what should I buy for my garage gym with $1,500") and states what input the agent must supply. It also covers the edge case of no budget being supplied. It gives no guidance on when to prefer answer_home_gym_question or build_home_gym over this tool, so routing against siblings is left to inference.

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