formtrace-mcp

by arciomdavydau

Overview Schema Source Related Servers Discussions Admin

Python

Local

List Hevy Routines

list_hevy_routines

Read-only

Retrieve a paginated list of saved Hevy routines to browse or select routines for workout planning and management.

Instructions

Get a page of saved Hevy routines; page_size is at most 10.

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

Input Schema

Name	Required	Description	Default
`page`	No
`page_size`	No

Output Schema

Name	Required	Description	Default
`data`	Yes
`source`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Nov 10, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered. The description does add one genuinely useful behavioral constraint beyond the schema: page_size is capped at 10. It says nothing about ordering, what a page contains, or how to detect the end of the collection, so the added context is modest.

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?

A single short sentence with the key constraint front-loaded, and no filler. It is efficient, though the terseness leaves gaps that a slightly longer description could have closed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return-value detail is not required, and annotations cover the safety profile. What remains missing for a paginated listing tool is pagination semantics (page indexing and termination) and how results are ordered. Adequate to call, but not 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 0%, so the description must compensate. It documents the page_size maximum of 10, which the schema omits (it only supplies a default). However, the 'page' parameter is left completely unexplained, including whether it is 1-based and what happens past the last page, so compensation is only partial.

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?

The description gives a specific verb and resource plus scope: 'Get a page of saved Hevy routines'. The word 'page' and 'saved' distinguish it from a single-routine getter and from creation tools. It stops short of naming any sibling explicitly, so it is clear but not fully differentiated.

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

Usage Guidelines2/5

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

It states no when-to-use context and no exclusions. An agent must infer that this is the bulk-listing tool and that get_hevy_routine should be used for a single routine. Nothing in the text routes between alternatives or mentions prerequisites.

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