Skip to main content
Glama

Personal records

get_personal_records
Read-only

The user's best lifts over a period: heaviest weight and best estimated 1-rep max per exercise, with the date it happened.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_personal_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoHow far back. Default 365.
limitNoHow many exercises, by best 1RM. Default 15.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description adds useful output semantics (one record per exercise, each with its occurrence date), but says nothing about ordering, aggregation across the window, or what happens when no data exists in the period.

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?

A single front-loaded sentence that defines the result set and each field without any filler. Nothing is redundant with the title in a wasteful way.

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

Completeness4/5

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

With no output schema, the description usefully enumerates the returned fields and the per-exercise granularity, and both optional parameters are fully specified in the schema. Minor gaps remain around empty results and tie-breaking/ordering, but nothing needed to invoke the tool 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 coverage is 100%, so the schema already documents days and limit with their bounds and defaults; the description only gestures at 'over a period.' Baseline 3 applies since the schema does the heavy lifting and the description adds no extra parameter meaning.

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 names a specific resource and result shape: heaviest weight and best estimated 1RM per exercise with the date. An agent can tell it returns records rather than progress or workouts. It stops short of naming which sibling (e.g., get_exercise_progress) covers trend-over-time instead, so 4 rather than 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'best lifts over a period' suggests you call it when asked for personal bests. There is no explicit when-to-use, no when-not-to-use, and no pointer to an alternative for per-session or trend queries.

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.

Resources