Skip to main content
Glama

Get Lifting Breakdown

get_lifting_breakdown

Break down lifting volume and session counts by weekday, program, muscle, or exercise for a date range to identify training patterns and focus areas.

Instructions

Volume and session counts split by weekday, program, muscle or exercise.

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_breakdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax rows to return; default from DEFAULT_PAGE_LIMIT
programNoFilter to one program
end_dateYesDate as YYYY-MM-DD
dimensionNoweekday | program | muscle | exerciseexercise
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.1/5.0
Behavior2/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 identifies the metrics and grouping dimensions but does not state read-only behavior, pagination defaults, date-range semantics, or any other operational traits beyond what the schema already declares.

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 description is a single efficient sentence with no filler. It front-loads the key metrics and grouping options, and every word contributes to the purpose.

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, so return values need not be explained. However, with no annotations and no usage guidance, the definition leaves important context about when and how to use this aggregation tool under-specified.

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 five parameters, including the dimension enum and date formats. The description echoes the dimension choices but adds no new semantics beyond the structured schema.

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 resource and scope: volume and session counts grouped by weekday, program, muscle, or exercise. It is clear what the tool returns, though it does not explicitly distinguish itself from siblings like get_lifting_summary or get_lifting_trend.

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 guidance on when to use this tool versus alternatives such as get_lifting_summary or get_lifting_trend. The description implies it is a breakdown/aggregation tool but gives no conditions, exclusions, or decision rules.

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