Skip to main content
Glama

Get Lifting Summary

get_lifting_summary

Summarize lifting performance for a date range, including totals, top exercises, muscle balance, and weekly volume to track training progress.

Instructions

Lifting totals, top exercises, muscle balance and weekly volume.

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

Input Schema

NameRequiredDescriptionDefault
top_nNoTop exercises to list
end_dateYesDate as YYYY-MM-DD
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

C2.5/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden, and it discloses almost nothing: no indication that this is a read-only aggregation, no note on cost/latency, no statement that both dates are mandatory, and no disclosure of what the weekly-volume bucketing assumes. The only implicit signal is the 'get_' prefix. This is a substantial gap for a tool with zero annotation coverage.

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?

It is a single short fragment with no filler, but the brevity is under-specification rather than economy: it is not front-loaded with a purpose statement because there is no purpose statement at all.

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?

An output schema exists, so return values need not be explained, and the input schema is fully described. But the description leaves the agent unable to route between the lifting siblings or to know that a date range is required, which is the minimum context a three-parameter aggregation tool should carry.

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 start_date, end_date and top_n with formats and bounds. The description adds no meaning beyond that — it does not explain whether the date range is inclusive, how top_n interacts with 'top exercises', or what a 'week' boundary is — so the baseline 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 is a noun phrase enumerating the contents of the result ('Lifting totals, top exercises, muscle balance and weekly volume') rather than a verb-plus-resource statement. It does tell an agent what data comes back, which is more than a tautology, but it never says what the tool actually does (aggregate? compute? retrieve?) and gives no basis for distinguishing it from get_lifting_breakdown 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 when-to-use, when-not-to-use, or alternative-routing guidance anywhere in the description. With seven sibling tools covering lifting data and overview/status, the agent is left to infer entirely from the name which one to pick.

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