Skip to main content
Glama
Sign In
mcp-server-hevy

mcp-server-hevy

by borgels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get User Info

hevy_get_user_info
Read-onlyIdempotent

Fetch your Hevy profile information, including user ID, display name, and profile URL, to access your strength-training account via MCP.

Instructions

Your Hevy profile (id, name, profile URL).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds the return fields (id, name, profile URL), which is helpful since there is no output schema. However, it does not elaborate on authentication requirements or any behavior beyond the raw output.

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?

The description is a single short sentence that is immediately informative. It contains no filler and presents the core information upfront.

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?

For a simple parameterless getter with rich annotations, the description adequately states the resource and expected output fields. It could explicitly say 'authenticated user' but 'Your' implies that context. The lack of an output schema makes the field list valuable, but no further behavioral details are needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With zero parameters, the schema is fully complete (100% coverage). The description correctly avoids inventing parameter details. The baseline for parameterless tools is 4, and nothing reduces that.

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 states the resource ('Your Hevy profile') and the specific fields ('id, name, profile URL'), making it clear this tool retrieves the current user's profile. It distinguishes from siblings like hevy_get_workouts and hevy_get_routines, which target different resources. The absence of an explicit verb is acceptable given the tool name.

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?

The description gives no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or the context of being connected. The intended usage is only implied by the tool name and the broad set of sibling tools.

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