openGym MCP Bridge

get_summary

Retrieves a read-only summary by counting routines and workouts and returning only the latest workout and latest body weight.

Instructions

Read-only. Count routines and workouts; show only the latest workout and latest body weight.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.4.1Oct 27, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations at all, the description does real work: it declares 'Read-only' and discloses the aggregation and truncation behavior (counts plus only the latest records). It leaves out any statement about scope of the counts (all-time vs. recent) or error behavior, which keeps it below a 5.

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?

Two short clauses, safety note front-loaded, then the exact output shape. Every word earns its place with no filler.

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?

For a no-parameter tool with no output schema, the description adequately conveys what comes back: two counts plus the latest workout and latest body weight. Only the time window of those counts is left unstated, a minor gap for a simple summary tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema is trivially complete and the description has nothing to compensate for. Baseline 4 applies since no parameter guidance is needed.

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?

States a specific action set: count routines and workouts, and return only the latest workout and latest body weight. That is concrete enough to separate it from list-style siblings like get_recent_workouts or list_workouts, though it never names those siblings explicitly.

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 by the phrase 'show only the latest workout', which suggests this is the lightweight overview rather than a full listing. There is no explicit when-to-use, when-not-to-use, or named alternative (e.g. get_weekly_training_summary) despite several summary-adjacent siblings.

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