Strong Saga Home Gym Gear Finder

Build a starter home gym

build_home_gym

Read-only

Use when a user asks what to buy for a home gym within a budget and space, e.g. "I have $1,000, an 8 ft ceiling and an 8x10 ft corner, what should I get?" or "best cardio machine for $600 in a small room". Returns a starter set chosen only from products whose stored guide data fits the limits: goal strength gives a barbell setup (rack or stand, bench, barbell and plates) or a dumbbell setup (bench and adjustable dumbbells); cardio gives one machine; both gives a strength setup plus a cardio machine. Each item has why_it_fits (from the data) and guide_url; total sums the guide price ranges; skipped lists items left out and why (for example price not stated in guide); budget_needed says what a full set starts at. Add folds_away=true for a set that folds away, or wall_mount=false for renters who cannot drill. Pass quiet, apartment, user_weight_lbs or min_capacity_lbs to fit noise, apartment and weight limits.

Input Schema

Name	Required	Description	Default
`goal`	No		strength
`quiet`	No	true keeps cardio machines a guide calls quiet and drops anything a guide calls loud (such as iron plates).
`budget`	Yes	Total USD for the whole set, e.g. 1000.
`floor_ft`	No	Free floor area as width x length in feet, e.g. 8x10.
`apartment`	No	true builds a dumbbell-based set (the Strong Saga $500 guide advises this for a spare room or apartment), skips gear a guide says to skip in an apartment, and keeps cardio a guide names for apartments or calls quiet.
`ceiling_in`	No	Ceiling height in inches (8 ft = 96).
`folds_away`	No	true picks only a rack, bench and cardio machine whose guide says they fold or store upright.
`wall_mount`	No	false skips anything the guide says mounts to a wall (renters). true keeps only wall-mounted racks.
`user_height_in`	No	User height in inches, used for treadmill and walking pad ceiling math.
`user_weight_lbs`	No	User's body weight in lb; the bench and cardio machine must list at least this capacity.
`min_capacity_lbs`	No	Minimum listed rating for the rack or stand, in lb.

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedOct 25, 2026

addedInput schema / properties / apartment

Added value: +{
+  "description": "true builds a dumbbell-based set (the Strong Saga $500 guide advises this for a spare room or apartment), skips gear a guide says to skip in an apartment, and keeps cardio a guide names for apartments or calls quiet.",
+  "type": "boolean"
+}

addedInput schema / properties / min_capacity_lbs

Added value: +{
+  "description": "Minimum listed rating for the rack or stand, in lb.",
+  "type": "number"
+}

addedInput schema / properties / quiet

Added value: +{
+  "description": "true keeps cardio machines a guide calls quiet and drops anything a guide calls loud (such as iron plates).",
+  "type": "boolean"
+}

addedInput schema / properties / user_weight_lbs

Added value: +{
+  "description": "User's body weight in lb; the bench and cardio machine must list at least this capacity.",
+  "type": "number"
+}

Changed2 schema fields changedOct 25, 2026

addedInput schema / properties / folds_away

Added value: +{
+  "description": "true picks only a rack, bench and cardio machine whose guide says they fold or store upright.",
+  "type": "boolean"
+}

addedInput schema / properties / wall_mount

Added value: +{
+  "description": "false skips anything the guide says mounts to a wall (renters). true keeps only wall-mounted racks.",
+  "type": "boolean"
+}

AddedOct 25, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds substantial behavioral detail beyond them: how goal selects different set compositions, what why_it_fits/guide_url/total/skipped/budget_needed contain, and how flags like folds_away and wall_mount alter selection. This is unusually rich context for a read-only tool.

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 trigger is front-loaded and the output contract is stated early, so the most important information comes first. The single dense paragraph includes two long quoted examples and many output-field details; most of it earns its place, but it could be more scannable.

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?

There is no output schema, and the description compensates by enumerating the return fields (why_it_fits, guide_url, total, skipped, budget_needed) and explaining what each means. For an 11-parameter tool with only readOnly/openWorld annotations, this gives an agent enough to call and interpret it correctly.

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 description coverage is already 91%, so the baseline is 3. The description still adds meaningful parameter-related context by explaining that 'goal strength' yields a barbell or dumbbell setup, 'cardio' yields one machine, and 'both' combines them – details not present in the schema's enum-only goal field – while tying quiet, apartment, user_weight_lbs and min_capacity_lbs to filtering behavior.

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?

The description gives a specific verb and resource ('build a starter home gym') and explains exactly what the tool returns: a starter set filtered by budget/space and goal. It implicitly distinguishes itself from answer_home_gym_question by describing structured output, but it does not explicitly name that sibling as an alternative.

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?

It opens with an explicit 'Use when...' trigger and supplies two representative user queries, so an agent can recognize the intended scenario. It does not state when not to use it or name alternatives like answer_home_gym_question, so it falls short of a full routing guideline.

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

All Strong Saga Home Gym Gear Finder tools Inspect

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

Need Help?