Phorme Training

Preview workout in Phorme

preview_workout_import

Use this when the user wants a single workout they can follow and track in Phorme: one written in this conversation, pasted from notes, or built to fit their time and equipment. It checks the workout, matches each exercise to the Phorme movement library with a demo link, flags anything that needs equipment the user did not list or runs past their time, and stores a private preview for 24 hours. It does not save training to any account. Do not use it for multiweek programs, nutrition plans, or pain and injury questions.

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": {
      "workout": "<workout>"
    },
    "name": "preview_workout_import"
  }
}

Input Schema

Name	Required	Description
`origin`	No	Use "sport_week" when the workout is a session returned by preview_sport_week. Otherwise leave out.
`workout`	Yes	The workout to preview, taken from this conversation.
`time_limit_minutes`	No	Minutes the user said they have. Leave out when the user did not say.
`available_equipment`	No	Equipment the user said they have, for example ["dumbbells", "bench"] or ["none"]. Leave out when the user did not say.

Output Schema

Name	Required	Description
`title`	Yes
`warnings`	Yes	Items the user should review before saving.
`exercises`	No	Each exercise with its Phorme library match and demo link.
`expires_at`	Yes	When the preview can no longer be saved, as an ISO 8601 time.
`preview_id`	Yes	Identifies this preview when it is saved.
`training_kind`	Yes
`warning_count`	Yes
`exercise_count`	Yes
`requires_confirmation`	Yes	Always true: saving needs the user's confirmation.
`estimated_duration_minutes`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedOct 16, 2026

changedOutput schema / properties / exercises / description

Previous value: -"Each exercise with its Phorme library match. Share the demo_url links with the user."New value: +"Each exercise with its Phorme library match and demo link."

changedOutput schema / properties / preview_id / description

Previous value: -"Pass this to the matching save tool after the user confirms."New value: +"Identifies this preview when it is saved."

changedOutput schema / properties / requires_confirmation / description

Previous value: -"Always true. Ask the user before saving."New value: +"Always true: saving needs the user's confirmation."

First observedOct 7, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false/destructiveHint=false/openWorldHint=false but say nothing about persistence. The description fills that gap: the preview is stored privately for 24 hours and no training is saved to any account, which resolves whether the write is durable. It stops short of stating auth requirements or what happens on expiry, so it lands just under a 5.

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?

Four sentences, front-loaded with the selection trigger before the behavior list and the exclusions. The middle sentence is dense with comma-separated clauses but each clause carries distinct operational information, so nothing reads as filler.

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 tool with 4 parameters, a nested workout object, and an output schema (so return values need no prose), the description covers scope, transformations performed, storage lifetime, persistence boundary, and exclusions. An agent has everything needed to decide and invoke 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 100%, so the baseline is 3. The description goes further by explaining the effect of the optional inputs: it checks for equipment the user did not list and for workouts running past their stated time, which clarifies why time_limit_minutes and available_equipment exist rather than just what they accept.

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?

States a specific verb and resource ('preview a single workout in Phorme') and enumerates the concrete work performed: validates the workout, maps exercises to the Phorme movement library with demo links, flags equipment/time conflicts, and stores a private 24-hour preview. This is clearly distinguishable from siblings like save_workout_to_phorme, preview_program_import, and preview_sport_week.

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

Usage Guidelines5/5

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

Gives explicit when-to-use triggers (workout written in conversation, pasted from notes, or built to fit time/equipment) and explicit when-not conditions ('Do not use it for multiweek programs, nutrition plans, or pain and injury questions'). The exclusions route the agent away from this tool for adjacent requests, which is exactly what selection guidance should do.

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

All Phorme Training 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.