Skip to main content
Glama

Povver — Strength Training

Query Sets

query_sets
Read-only

Query raw set-level training data with flexible filters: by exercise name (fuzzy), muscle group, specific muscle, or exercise IDs. Returns individual set records with weight, reps, RIR, date, exercise info, and rest: rest_s = seconds rested BEFORE this set (gap from the previous completed set of the same exercise by tick time; null on the first set of an exercise, on sets ticked in bulk, and on gaps over 30 min — null means "not a rest", never 0) and rest_target_s = the timer target the user was given for it (null when no timer ran; absent on sets logged before rest timers shipped). Use for custom analysis, data export, or when you need granular training data that the higher-level tools don't cover. Max 200 results PER PAGE — when the response has truncated=true, pass its next_cursor back as cursor (keeping every other argument identical, including sort) to read the next page. PROVENANCE: filtering by muscle_group or muscle matches ANY involvement (primary mover OR synergist), not just direct work — the response declares meta.counting_basis and annotates each row with contribution (0-1), plus is_primary on the muscle_group path; for a landmark-comparable count keep is_primary=true rows. Filtering by exercise_name returns meta.resolution naming the exercise_id(s) actually read, whether the name was ambiguous, and the runner-up candidates — check it before trusting a name-filtered result, and re-query by exercise_ids for an exact lift. Each row also carries measure ('reps' | 'duration' | 'distance'; absent means reps), duration_s and distance_m for timed/distance sets, and effective_load_kg when present (absent on older sets — read weight_kg then). On a duration or distance set, reps is NOT a rep count and e1rm is not meaningful (ignore it even when present): read duration_s / distance_m instead.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoSort order (default date_desc). Must stay the SAME across a paginated sequence — the cursor encodes it.
limitNoMax results (max 200)
cursorNoPass the `next_cursor` from a previous response to fetch the next page. Omit for the first page.
muscleNoSpecific muscle (e.g., "posterior deltoid")
exercise_idsNoExercise IDs (max 10)
muscle_groupNoMuscle group (e.g., "chest", "back", "shoulders")
exercise_nameNoExercise name (fuzzy match)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataNo
metaNo
successNo
truncatedNo
next_cursorNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint/openWorldHint; the description carries the real behavioral load. It defines null semantics for rest_s ('null means not a rest, never 0'), pagination truncation behavior, muscle_group/muscle matching that includes synergists, meta.counting_basis and meta.resolution provenance, and the fact that reps/e1rm are meaningless on duration or distance sets.

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?

Long but information-dense, with purpose front-loaded and the pagination rule and provenance caveats each earning their space. Some return-field detail (rest_s/rest_target_s null cases, measure/e1rm notes) overlaps with what an output schema should carry, which keeps it from a 5.

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?

Given an output schema and read-only annotations exist, the description is complete enough for correct invocation: filtering semantics, pagination mechanics, provenance caveats, and the trap cases (duration/distance sets, ambiguous names) are all covered.

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 coverage is 100%, so the baseline is 3. The description still adds value beyond the schema: it warns that sort must stay constant across a paginated sequence, that cursor pairs with truncated/next_cursor, and that muscle_group filtering has a non-obvious any-involvement semantics that the schema's 'Muscle group' description does not convey.

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 ('Query raw set-level training data') plus its filter dimensions (exercise name, muscle group, muscle, exercise IDs). It explicitly contrasts itself with 'the higher-level tools' in the sibling list, so an agent can distinguish it from get_exercise_progress or get_muscle_group_progress without opening a schema.

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?

Gives clear contexts ('custom analysis, data export, or when you need granular training data that the higher-level tools don't cover') and operational guidance for pagination (pass next_cursor, keep all other args identical including sort) and for re-querying by exercise_ids when a name match is ambiguous. It stops short of naming a specific sibling tool for each alternative scenario, which is what a 5 requires.

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.