Skip to main content
Glama

gymvio_open

Open a Gymvio page in a signed-in cloud browser to review client check-ins and workout logs, prepare training and nutrition plans, or draft messages.

Instructions

Open a Gymvio page in your signed-in Cloud Browser (default https://gymvio.com/login) to work with review client check-ins and workout logs, prepare training and nutrition plans and draft messages.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://gymvio.com/login

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/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 burden. It usefully discloses that the browser is signed in (pre-authenticated session) and that a URL can be overridden, which is real behavioral context. It does not say what happens on an invalid/unreachable URL, whether navigation discards prior page state, or what the tool returns.

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?

One sentence, front-loaded with the verb and core action, then the default, then the motivating use cases. No filler or repetition. The use-case list is slightly long but stays within a single readable clause.

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 one-optional-parameter navigation tool with no output schema, the description covers what it does, the default target, and why an agent would open it. The main omission is ordering relative to companion tools (click/read/type operating on the opened page), which would help but is not strictly required.

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 coverage is 100% and the single url parameter is already documented with its default, so the description's restatement of the default adds nothing new. No guidance on accepted URL formats (absolute vs relative, allowed hosts) appears in either place. Baseline 3 is appropriate.

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?

States a concrete verb and resource: open a Gymvio page in a signed-in Cloud Browser, with the default target URL given inline. It also names the domain activities (check-ins, workout logs, plans, messages), so the agent knows the kind of work this tool enables. It does not explicitly differentiate itself from gymvio_click/read/type, but 'open a page' is distinct enough in plain language.

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?

Usage is implied rather than stated: the purpose clause suggests this is the entry point for acting on Gymvio content, but there is no explicit 'call this first before gymvio_click/gymvio_read' instruction and no exclusions. An agent can infer when to use it but must guess its position in the workflow.

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