Skip to main content
Glama

gymvio_click

Clicks a specified numbered element on the current Gymvio page, enabling AI agents to interact with the intended control after reading the page.

Instructions

Click a numbered element on the current Gymvio page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>"
    },
    "name": "gymvio_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and largely fails to: it does not say whether a click navigates, submits a form, or otherwise mutates state, nor what happens if the element number is stale or out of range. The only behavioral hint, that numbering derives from the last read, comes from the schema rather than the description.

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 front-loaded sentence with no filler, and the target ('numbered element on the current Gymvio page') is stated before anything else. Its brevity borders on under-specification, but nothing extraneous is present.

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?

For a one-parameter action tool with no annotations and no output schema, the definition covers what is clicked but not the consequences or failure modes of clicking. Adequate to invoke correctly in the happy path, incomplete for an agent that needs to reason about side effects or stale element references.

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?

With one parameter at 100% schema description coverage, the schema already explains that 'element' is an integer drawn from the last read. The description adds no further semantics such as whether numbering is stable across reloads or what error a stale index produces.

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 specific verb (Click) and a specific target (a numbered element on the current Gymvio page), which is more precise than a bare name restatement. It implicitly separates itself from gymvio_read (which produces the numbering) and gymvio_type, but never names a sibling or states the distinction 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?

Usage is only implied: the agent must infer that a prior gymvio_read is required to obtain element numbers, an inference supported by the schema note 'Element number from the last read' rather than by the description. There is no statement of when to prefer this over gymvio_type or what to do if the page has not been read yet.

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