Skip to main content
Glama

gymvio_guide

Guides you through Gymvio coach workflows: review check-ins and workout logs, prepare training and nutrition plans, draft messages, and locate the sign-in link. Call this first.

Instructions

How to work in Gymvio (review client check-ins and workout logs, prepare training and nutrition plans and draft messages): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Gymvio, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full disclosure burden. It does reveal what the tool surfaces (screens and the sign-in link), which signals it is an informational/orientation tool rather than a mutation, but it says nothing about whether calls have side effects, how large the returned content is, or whether the guidance persists after the first call.

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?

Two sentences: the first front-loads scope and covered capabilities, the second delivers the critical 'Call this first' instruction. The dense parenthetical is slightly packed but every element maps to a real capability; nothing is filler.

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 low-complexity orientation tool with one optional parameter and no output schema, the description covers what it does, what it returns (screens, sign-in link), and when to invoke it. A minor gap is whether orientation must be repeated or is one-time per context.

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?

There is a single optional 'task' parameter with 100% schema coverage, so the schema already documents it. The description's parenthetical capability list loosely maps to the kinds of tasks accepted but adds no format, granularity, or phrasing guidance beyond the schema's 'in your words'.

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 uses a clear framing ('How to work in Gymvio') and enumerates concrete capabilities it covers: reviewing client check-ins and workout logs, preparing training and nutrition plans, drafting messages, plus screens and sign-in link. This distinguishes it from the action-oriented siblings (click, type, read), though the core verb 'guide' is more informational than action-specific.

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

Usage Guidelines4/5

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

The closing directive 'Call this first' gives explicit sequencing guidance relative to the sibling action tools. It doesn't spell out when not to call it (e.g., after orientation is complete) or whether it should be re-called per session, but the primary usage instruction is unambiguous.

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