Skip to main content
Glama

Chart my lift progress

get_lift_progress
Read-only

Use this when the user asks how one of their lifts is progressing or wants it graphed, for example "how is my bench going" or "chart my squat over six months". It finds the lift in their Phorme log by the words they use and returns one point per session with the best set, estimated max and volume, the change over the period and their best session, and shows a chart card. It reads only and changes nothing. It needs a connected Phorme account. Weights are in pounds. If no lift matched it lists the lifts they have logged.

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": {
      "movement": "<movement>"
    },
    "name": "get_lift_progress"
  }
}

Input Schema

NameRequiredDescriptionDefault
monthsNoHow many months back to look. Defaults to 6.
movementYesThe lift as the user said it, for example "bench", "back squat" or "RDL".

Output Schema

NameRequiredDescriptionDefault
bestNo
foundYes
changeNofrom_e1rm_lb, to_e1rm_lb, change_lb and change_pct over the period.
pointsNoOldest first: on, top_set, e1rm_lb, volume_lb, sets.
movementNoThe logged lift that matched, or null.
also_matchedNoOther logged lifts the words also matched.
logged_movementsNoWhen nothing matched: the lifts they log most.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds useful context beyond annotations: it needs a connected Phorme account, weights are in pounds, it emits a chart card, and it lists logged lifts on no match. Does not discuss rate limits or pagination, but coverage is strong for a read-only tool.

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?

A single dense paragraph, front-loaded with the trigger condition. Every sentence carries information; minor density but no waste.

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?

With an output schema present, the description needn't detail return values, and it still gives account prerequisite, unit system, chart card behavior, and empty-match fallback. Nothing an agent needs to call it correctly is missing.

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 description coverage is 100%, so the schema already documents both parameters including the months default. The description reinforces the movement matching behavior (finds by the words the user uses) but does not add syntax or format beyond the schema. Baseline 3 is right.

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 (chart/find) and resource (lift progress) and distinguishes itself from siblings like get_training_history and get_planned_sessions by returning per-session data points plus a chart. The description makes clear what it returns (one point per session with best set, estimated max, volume) so an agent can pick it without opening the schema.

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 user-phrasing triggers ("how is my bench going", "chart my squat over six months") and the condition for the no-match fallback. Practical routing guidance beyond mere purpose.

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.