Strong Saga Home Gym Gear Finder

What changed in the gear data

get_gear_changes

Read-only

Use to check whether cached Strong Saga gear data is still current, or when a user asks what is new. Returns each data refresh newest first: products added or removed (ids), prices added or changed, guide ranks changed, guides updated, fields added, with the UTC time and API version. Built only from this API's own refresh history. Pass since (YYYY-MM-DD) for refreshes after a date, or id for one product.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_gear_changes"
  }
}

Input Schema

Name	Required	Description	Default
`id`	No	Only refreshes that touched this product id, e.g. sg-001.
`since`	No	Only refreshes at or after this date (YYYY-MM-DD) or UTC time (YYYY-MM-DDTHH:MM:SSZ).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedNov 1, 2026
- addedInput schema / properties / id / examples
```
Added value: +[
+  "sg-001"
+]
```
- addedInput schema / properties / since / examples
```
Added value: +[
+  "2026-10-25"
+]
```
AddedOct 26, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already establish read-only and closed-world behavior. The description adds valuable context beyond those annotations by disclosing return contents, ordering, UTC timestamps, API version, and that the history is built only from this API's own refresh data.

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 front-loaded with the use case, then explains return shape, data provenance, and parameter shortcuts. It is tight and no sentence is extraneous.

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 simple read-only query with only two optional parameters and no output schema, the description provides enough detail about purpose, return contents, ordering, and filtering 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 coverage is 100%, and both parameters already have descriptions and examples. The description summarizes 'since' and 'id' usage but mostly repeats what the schema provides, with a minor wording difference: 'after a date' versus the schema's 'at or after.'

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 uses a specific verb-and-resource framing: check whether cached Strong Saga gear data is current and see what changed. It clearly distinguishes this change-history tool from sibling gear lookup/search tools by focusing on refresh events rather than gear records.

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 gives explicit use cases: checking whether cached data is current and answering 'what is new.' It does not name sibling alternatives or when-not to use it, so it falls short of full routing guidance.

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?