Skip to main content
Glama

Get Lifting Sessions

get_lifting_sessions

Retrieve paginated lifting sessions within a date range, filter by muscle, exercise, program, or weighted sets, and optionally expand sets for up to 10 sessions.

Instructions

Paginated lifting sessions; include_sets expands up to 10 sessions.

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

Input Schema

NameRequiredDescriptionDefault
sortNoSort key, '-' prefix for descendingdate
limitNoMax rows to return; default from DEFAULT_PAGE_LIMIT
muscleNoFilter to one muscle group
offsetNoSkip first N sessions
programNoFilter to one program
end_dateYesDate as YYYY-MM-DD
exerciseNoFilter to one exercise
weightedNoOnly weighted sets
start_dateYesDate as YYYY-MM-DD
include_setsNoExpand sets for at most 10 sessions

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations provided, the description carries the full behavioral burden but delivers almost nothing. The only behavioral claim (include_sets caps at 10 sessions) merely restates the include_sets schema description, and there is no disclosure of read-only nature, permission needs, or how pagination interacts with limit/offset.

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

Conciseness3/5

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

The single clause contains no filler and is front-loaded, but for a ten-parameter tool with two required date parameters it is under-specified rather than appropriately concise. Brevity here costs more than it saves.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has ten parameters, two of them required, filtering options, pagination, and no annotations, yet the description covers none of the required date range or filters. An output schema exists so return values need not be explained, but the input and behavioral picture is significantly incomplete.

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 all ten parameters, including the sort enum and limit/offset, are already documented in the schema. The description adds no meaning beyond that and only echoes the include_sets cap, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ("lifting sessions") and one retrieval trait ("paginated"), which separates it loosely from summary/trend/breakdown siblings. However, it uses no verb and never states that it returns raw session records over a required date range, so the agent must infer scope from the name and schema.

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 when-to-use guidance and no mention of the sibling tools that could otherwise serve the request (get_lifting_summary, get_lifting_breakdown, get_lifting_trend). Nothing indicates that start_date and end_date are mandatory or how this differs from a summary/breakdown call.

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