Create a new workout routine for your Hevy account by providing a title and exercises with sets. Optionally assign to a folder, and receive the routine ID.
Create a new workout routine in your Hevy account. Requires a title and at least one exercise with sets. Optionally assign to a folder. Returns the full routine details including the new routine ID.
| Name | Required | Description | Default |
|---|---|---|---|
| notes | No | ||
| title | Yes | ||
| folderId | No | ||
| exercises | No |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
v1.23.8Input schema / additionalPropertiesRemoved value: -falseInput schema / properties / exercises / items / additionalPropertiesRemoved value: -falseInput schema / properties / exercises / items / properties / restSeconds / maximumAdded value: +9007199254740991Input schema / properties / exercises / items / properties / sets / items / additionalPropertiesRemoved value: -falseInput schema / properties / exercises / items / properties / sets / items / properties / distanceAdded value: +{
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+}Input schema / properties / exercises / items / properties / sets / items / properties / distanceMeters / maximumAdded value: +9007199254740991Input schema / properties / exercises / items / properties / sets / items / properties / distanceMeters / minimumAdded value: +-9007199254740991Input schema / properties / exercises / items / properties / sets / items / properties / durationAdded value: +{
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+}Input schema / properties / exercises / items / properties / sets / items / properties / durationSeconds / maximumAdded value: +9007199254740991Input schema / properties / exercises / items / properties / sets / items / properties / durationSeconds / minimumAdded value: +-9007199254740991Input schema / properties / exercises / items / properties / sets / items / properties / repRangeAdded value: +{
+ "properties": {
+ "end": {
+ "anyOf": [
+ {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "start": {
+ "anyOf": [
+ {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ }
+ },
+ "type": "object"
+}Input schema / properties / exercises / items / properties / sets / items / properties / reps / anyOfAdded value: +[
+ {
+ "maximum": 9007199254740991,
+ "minimum": -9007199254740991,
+ "type": "integer"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / exercises / items / properties / sets / items / properties / reps / typeRemoved value: -"integer"Input schema / properties / exercises / items / properties / sets / items / properties / weightAdded value: +{
+ "type": "number"
+}Input schema / properties / exercises / items / properties / supersetId / anyOfAdded value: +[
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / exercises / items / properties / supersetId / typeRemoved value: -[
- "number",
- "null"
-]Input schema / properties / folderId / anyOfAdded value: +[
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / folderId / typeRemoved value: -[
- "number",
- "null"
-]Input schema / requiredPrevious value: -[
- "title",
- "exercises"
-]New value: +[
+ "title"
+]v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate write operation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that it 'Returns the full routine details including the new routine ID,' which is useful but doesn't disclose other behavioral traits like authentication needs or side effects.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the main action, and contains no wasted words. Every sentence adds value.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a tool with 4 parameters, one required, and nested objects, the description covers the essential requirements and return value. However, it omits the notes parameter and could elaborate on folder behavior. Still, sufficient for an agent to understand the tool's role.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must compensate. It mentions the title is required, exercises need sets, and folder is optional, but doesn't detail the structure of exercises or other parameters like notes. This provides basic understanding but not thorough explanation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Create a new workout routine in your Hevy account.' It uses a specific verb ('Create') and resource ('workout routine'), and distinguishes from sibling tools like create-exercise-template or create-workout by specifying 'workout routine'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description explicitly states requirements: 'Requires a title and at least one exercise with sets. Optionally assign to a folder.' This gives clear context for when to use the tool, but doesn't mention when not to use or list alternative tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
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