Skip to main content
Glama
diecoscai

@diecoscai/hevy-mcp

by diecoscai

hevy_create_body_measurement

Create a new body measurement record for a specific date with optional metrics like weight, lean mass, and body circumferences. Returns a 409 error if a record already exists for that date.

Instructions

Create one body-measurements record (POST /v1/body_measurements). Required: date (YYYY-MM-DD). All metric fields are optional and nullable: weight_kg, lean_mass_kg, fat_percent, neck_cm, shoulder_cm, chest_cm, left_bicep_cm, right_bicep_cm, left_forearm_cm, right_forearm_cm, abdomen, waist, hips, left_thigh, right_thigh, left_calf, right_calf. If a record already exists for that date, the server returns 409 — use hevy_update_body_measurement instead. Dry-run by default: returns { dry_run: true, executed: false, ... } unless HEVY_MCP_ALLOW_WRITES=1 is set on the server process.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYesCalendar date in YYYY-MM-DD (rejected if not a real date).
hipsNo
waistNo
abdomenNo
neck_cmNo
chest_cmNo
left_calfNo
weight_kgNo
left_thighNo
right_calfNo
fat_percentNo
right_thighNo
shoulder_cmNo
lean_mass_kgNo
left_bicep_cmNo
right_bicep_cmNo
left_forearm_cmNo
right_forearm_cmNo
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses POST mutation, dry-run by default (with enablement), duplicate detection (409), and suggests update tool. Missing details on authentication, rate limits, or idempotency, but is strong overall.

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?

Four sentences long, front-loaded with purpose, then parameters, error handling, and dry-run behavior. No redundancy or unnecessary words.

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?

Given 18 parameters, no annotations, and no output schema, the description covers purpose, parameters, error handling, alternative tool, and dry-run. It could mention what the response contains (e.g., the created record) but is still fairly complete.

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 only 6% (only date described). The description lists all metric fields and clarifies they are optional and nullable, which adds value over the schema. However, no additional semantics or units beyond field names.

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

Purpose5/5

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

The description states 'Create one body-measurements record (POST /v1/body_measurements)', clearly specifying the verb and resource. It distinguishes from sibling hevy_update_body_measurement by referencing the alternative when a record already exists.

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

Usage Guidelines5/5

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

Explicit guidance: required date format, optional/nullable fields, mention of 409 conflict with alternative tool, dry-run default with write-enablement condition. Tells the agent when to use this tool and when to switch to update.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/diecoscai/hevy-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server