Hybriqx Workout Adaptation

scale_workout

Scale a CrossFit workout to available equipment and a target time.

    Args:
        original_wod: Raw text of the workout to adapt.
        available_equipment: Equipment available to the athlete.
        target_time_domain_mins: Desired workout duration, or null to preserve it.
        athlete_notes: Movement restrictions or injuries to treat as constraints.

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": {
      "original_wod": "<original_wod>",
      "available_equipment": "<available_equipment>"
    },
    "name": "scale_workout"
  }
}

Input Schema

Name	Required	Description	Default
`original_wod`	Yes
`athlete_notes`	No
`available_equipment`	Yes
`target_time_domain_mins`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 16, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the entire behavioral burden, and it largely deflects to the Args list. It discloses that null target time preserves the original duration and that notes act as constraints, but says nothing about whether anything is persisted, permissions, side effects, or the shape of the result.

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 purpose sentence is front-loaded and waste-free, and the Args block is a compact, scannable list. Slightly redundant with the measured, indented formatting, but nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter tool with no output schema and no annotations, the description covers inputs and intent but omits what the tool returns and any operational caveats. Adequate minimum coverage, with a clear gap on the return contract that no structured field fills.

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 0%, so the description must compensate, and it does: each of the four parameters gets a short gloss, including the non-obvious semantics that target_time_domain_mins=null preserves the workout duration and that athlete_notes are treated as hard constraints. It falls short of 5 only by not reconciling the stated null behavior with the schema default of 15.

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: 'Scale a CrossFit workout to available equipment and a target time,' which tells an agent exactly what transformation is produced. The sibling service_info is clearly unrelated, so no explicit differentiation is required, but the description stops short of a 5 by not clarifying scope on the returned artifact.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description never says when to reach for this tool versus alternatives, and the only sibling listed is service_info. No prerequisites, no exclusion conditions, and no guidance about when scaling is or isn't appropriate are provided.

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

All Hybriqx Workout Adaptation 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?