Skip to main content
Glama
Sign In
Bevel MCP

Bevel MCP

by JoshPopov
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get Bevel completed workouts

bevel_get_workout_history
Read-only

Retrieve completed strength workouts with dates, duration, effort, exercises, sets, reps, weight, and volume; filter by date range or exercise name for read-only history review.

Instructions

Lists completed strength workouts (most recent first): date, start time, duration, effort, and each exercise's sets with reps and weight in the unit you use, plus volume (reps × lb). Filter by date range or exercise name. Read-only.

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": "bevel_get_workout_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLast day (YYYY-MM-DD), inclusive.
fromNoFirst day (YYYY-MM-DD), inclusive.
limitNoMaximum workouts to return (default 10).
exerciseNoOnly sets whose exercise id/name contains this, e.g. legPress.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so the 'Read-only' sentence is redundant but consistent. The description adds genuinely useful behavior: results are ordered most recent first, weights follow the caller's unit, and a derived volume value is included — context an agent would not otherwise have.

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

Conciseness4/5

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

One dense but well-ordered sentence: return contents first, then filtering, then the read-only note. Nothing is wasted, though the parenthetical field list is tightly packed and could read more cleanly.

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 carries the burden of describing return values and does so concretely, including sort order and derived fields. The default page size and limit bounds are only in the schema, which is acceptable at 100% coverage.

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 baseline applies; the description only restates that date range and exercise name are the filters, adding no syntax or semantics beyond the schema. Minor inconsistency: it promises weight 'in the unit you use' but describes volume as 'reps × lb'.

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 verb and resource ('Lists completed strength workouts') and names the returned fields (date, start time, duration, effort, sets, volume). It does not explicitly distinguish itself from the sibling bevel_get_workout_data, which an agent could easily confuse for the same data.

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?

Says 'Filter by date range or exercise name' and 'Read-only', implying that filtering is the main selection mechanism. However, it never states when to use this vs bevel_get_workout_data or when-not to use it, so usage is inferred rather than directed.

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

Deploy Server

Other Tools