Skip to main content
Glama

Sigwren

A single run or strength session, in the Mindful Runner Way

get_single_workout
Read-onlyIdempotent

One session built the Mindful Runner Way. A run (kind "run", the default) is warm-up, main work and cool-down, each step with its length and its effort on a 0–10 scale (RPE) with words for how it feels, because Sigwren does not know the person's zones or paces. Use it for "give me a 45-minute easy run", "a hill session for an hour", "a threshold workout". Pass focus (easy, recovery, long, strides, hills, fartlek, tempo, threshold, speed, vo2max, race_pace, progression, downhill, descent_tempo) and optionally minutes. A strength session (kind "strength") is one of three: Runners Strength (session runners_strength — squat, hinge, single-leg, push, pull and core; variant "full" is six exercises, "short" the first four), Runners Glutes (runners_glutes) or Max Strength (max_strength — heavy lifting, only for people who already lift with good technique). Each exercise comes with sets, reps, rest and its effort in reps left in the tank, because Sigwren does not know the person's maxes. The answer states how long the session takes. Use it for "a strength session for runners", "a quick strength routine" (variant short), "a glute workout". It needs no account and knows nothing about the person. It returns the session and the Mindful Runner workout contract: present the session in that order — a brief description, then Intent, Focus, Practice and Reflect as one short paragraph each, then the steps or exercises — in the Mindful Runner voice, with the numbers only in the steps or exercises, never in the paragraphs. You write the words; the sessions are Sigwren's. For Max Strength, open with its safety line.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNo"run" (the default) or "strength".
focusNoWhat the run is for: easy (the default), recovery, long, strides, hills, fartlek, tempo, threshold, speed, vo2max, race_pace, progression, downhill, descent_tempo.
minutesNoHow long the run should be, in minutes. Leave it out to get the length the Mindful Runner Way builds for this session. Runs only: strength sessions are chosen with session and variant, and say how long they take.
sessionNoFor kind "strength": runners_strength (the default — squat, hinge, single-leg, push, pull and core), runners_glutes, or max_strength (heavy lifting, for people who already lift with good technique).
variantNoFor runners_strength only: "full" (the default, six exercises) or "short" (the first four: squat, hinge, single-leg, push). The answer says how long it takes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the read-only and idempotent annotations, the description adds important behavioral context: no account is needed, it knows nothing about the person, it returns the session plus a presentation contract, and Max Strength requires a safety line. This is richly transparent.

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 description is appropriately comprehensive for a complex tool, and the main purpose is front-loaded. However, it is one dense paragraph and repeats some enum values and defaults already present in the schema, so it could be tightened.

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, but the description fully explains the return shape and the required Mindful Runner presentation contract. An agent has enough information to invoke the tool and format the result correctly.

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

Parameters5/5

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

Schema coverage is already 100%, and the description still adds meaningful semantics: run versus strength modes, default behavior, when minutes applies, what session and variant mean, and how RPE and reps-in-reserve are used because no zones or maxes are known.

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 clearly establishes that this tool returns one run or strength session and explains the two modes in detail. It does not explicitly contrast itself with the race-planning siblings, but the resource is specific enough to distinguish it.

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 clear usage examples for both runs and strength sessions and explains how focus, minutes, session, and variant select the right output. It lacks explicit when-not-to-use guidance or named alternatives among the sibling tools.

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