Skip to main content
Glama

Get Lifting Trend

get_lifting_trend

Track lifting volume, sessions, volume per session, or training time across date ranges; group by program, muscle, or exercise and view 4-week moving averages for weekly buckets.

Instructions

One lifting metric over time. Week buckets also carry a 4-week moving average.

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": {
      "start_date": "<start_date>",
      "end_date": "<end_date>"
    },
    "name": "get_lifting_trend"
  }
}

Input Schema

NameRequiredDescriptionDefault
bucketNoBucket sizeweek
metricNovolume | sessions | volume_per_session | training_timevolume
programNoFilter to one program
end_dateYesDate as YYYY-MM-DD
group_byNoOptional split by program, muscle or exercise
max_pointsNoMax series points when include_series=true; default from DEFAULT_MAX_POINTS
start_dateYesDate as YYYY-MM-DD

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses one meaningful output behavior—week buckets include a 4-week moving average—but omits other relevant context such as date-range constraints, caching behavior, or expected response characteristics beyond what the output schema covers.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is two short, front-loaded sentences with no wasted wording. The most important scoping detail is stated first, followed by a useful exception for week buckets.

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?

An output schema exists and the parameter schema is fully described, so the description need not explain return values or parameter formats. However, for a seven-parameter analytics tool with no annotations, the description is thin on usage routing and behavioral context beyond the moving-average note.

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 input schema already documents all seven parameters. The description adds little parameter-level meaning beyond reinforcing that one metric is returned over time and that week buckets include a moving average.

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 states a specific verb/resource shape: one lifting metric over time, which clearly identifies a time-series trend query. It does not explicitly distinguish this from sibling tools like get_lifting_summary or get_lifting_breakdown, so it falls short of a 5.

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?

There is no explicit when-to-use guidance, no exclusions, and no routing to alternatives among the lifting-related siblings. The phrase 'over time' implies trend usage, but an agent must infer when this tool is preferable to get_lifting_summary or get_lifting_breakdown.

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