Skip to main content
Glama

gymvio_read

Read the current Gymvio page's text and numbered buttons, links, and fields, optionally within a single element.

Instructions

Read the current Gymvio page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

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?

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the shape of the result (text plus numbered buttons, links and fields), which hints that the numbering supports later index-based actions, but it says nothing about whether a page must be loaded, what happens if none is open, or whether the snapshot is fresh.

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?

It is a single front-loaded sentence with no filler, and the resource is stated before the returned content. It is terse to the point of omitting prerequisites, but there is no wasted wording to cut.

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?

With one optional, fully documented parameter and no output schema, the description covers the essential question of what the agent gets back. The remaining gap — the preconditions for reading a page and how element scoping interacts with the returned numbering — is modest for a tool this simple.

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 100% and the sole parameter (element, minimum 1) is documented in the schema itself. The description adds nothing about scoping a read to a single element, so it neither explains nor undercuts the schema — baseline 3 applies.

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 names a specific verb ("Read") and a specific resource ("the current Gymvio page"), then enumerates the content returned: text, numbered buttons, links and fields. That is enough to distinguish it from write-oriented siblings such as gymvio_click and gymvio_type, though it never names an alternative explicitly.

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?

The word "current" implies a page must already be open, which is useful context, and the read-only phrasing signals it is the inspection counterpart to gymvio_click/gymvio_type. However, the description never states the prerequisite (e.g., a page must be opened with gymvio_open first) or tells the agent when to prefer this over gymvio_status.

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