Skip to main content
Glama
chrisdoc

Hevy MCP

by chrisdoc
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Remote

create-workout

Create a workout in Hevy by specifying title, start and end times, and exercises with sets. Returns the workout details including the new ID.

Instructions

Create a new workout in your Hevy account. Requires title, start/end times, and at least one exercise with sets. Returns the complete workout details upon successful creation including the newly assigned workout ID.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleYes
endTimeYes
exercisesNo
isPrivateNo
startTimeYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed17 schema fields changedv1.23.8
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / description / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / exercises / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / exercises / items / properties / notes / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "string"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / exercises / items / properties / sets / items / additionalProperties
      Removed value: -false
    • changedInput schema / properties / exercises / items / properties / sets / items / properties / customMetric / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "number"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / exercises / items / properties / sets / items / properties / distance
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedInput schema / properties / exercises / items / properties / sets / items / properties / distanceMeters / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "integer"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / exercises / items / properties / sets / items / properties / duration
      Added value: +{
+  "anyOf": [
+    {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedInput schema / properties / exercises / items / properties / sets / items / properties / durationSeconds / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "integer"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / exercises / items / properties / sets / items / properties / reps / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "integer"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": -9007199254740991,
+    "type": "integer"
+  },
+  {
+    "type": "null"
+  }
+]
    • changedInput schema / properties / exercises / items / properties / sets / items / properties / rpe / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "number"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / exercises / items / properties / sets / items / properties / weight
      Added value: +{
+  "anyOf": [
+    {
+      "type": "number"
+    },
+    {
+      "type": "null"
+    }
+  ]
+}
    • changedInput schema / properties / exercises / items / properties / sets / items / properties / weightKg / anyOf
      Previous value: -[
-  {
-    "anyOf": [
-      {
-        "not": {}
-      },
-      {
-        "type": "number"
-      }
-    ]
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedInput schema / properties / exercises / items / properties / supersetId / anyOf
      Added value: +[
+  {
+    "type": "number"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedInput schema / properties / exercises / items / properties / supersetId / type
      Removed value: -[
-  "number",
-  "null"
-]
    • changedInput schema / required
      Previous value: -[
-  "title",
-  "startTime",
-  "endTime",
-  "exercises"
-]New value: +[
+  "title",
+  "startTime",
+  "endTime"
+]
  2. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Description adds value beyond annotations by specifying that creation requires valid data and returns the newly assigned ID. Annotations already indicate readOnlyHint=false and destructiveHint=false, so no contradiction. However, it does not mention auth needs or rate limits, which would elevate transparency further.

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 sentences, front-loaded with purpose, then requirements, then output. No redundant words. Efficient and clear.

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 no output schema, description appropriately states return value. Input complexity is high (nested arrays), but description covers core requirements. Missing details on description and isPrivate parameters, but overall adequate for a creation tool.

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 0%, so description must compensate. It mentions title, start/end times, and that exercises must have sets, covering 4 of 6 parameters (title, startTime, endTime, exercises). Missing description and isPrivate. This adds some meaning but is incomplete.

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?

Description clearly states the action 'Create a new workout', specifies the resource ('workout in your Hevy account'), and outlines requirements (title, times, exercises) and return value (workout details with ID). This distinguishes it from siblings like get-workout or update-workout.

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?

Description implies when to use (to create a workout) but does not explicitly state when not to use it or provide comparisons to siblings like create-routine or update-workout. No exclusions or alternatives mentioned, so guidance is limited.

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/chrisdoc/hevy-mcp'

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