Skip to main content
Glama

fitune_click

Click a numbered element on the current Fitune page to select it and trigger its action. Use the element number from the last read to navigate studio admin views.

Instructions

Click a numbered element on the current Fitune 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": "fitune_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?

With no annotations, the description carries the full burden and says nothing about side effects: whether a click may navigate away, open dialogs, wait for load, or fail if the element number is stale. Only the phrase 'current page' hints at session state, which is thin for an action that mutates page state.

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?

One short sentence with the action and target front-loaded and zero filler. Nothing could be removed without losing information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a browser-automation click with no annotations and no output schema, the definition omits the prerequisite read, the post-click behavior (navigation, dialogs, waiting), and failure modes for stale element numbers. Low parameter complexity keeps the cost down, but the behavioral picture is incomplete.

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%, so the single 'element' parameter is already fully documented including its 'from the last read' origin. The description's 'numbered element' is consistent with the schema but adds no meaning beyond it.

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 pairs the specific verb 'click' with a specific resource, 'a numbered element on the current Fitune page,' so the agent knows exactly what action is performed and against what scope. It is clear without needing the schema, though it doesn't explicitly contrast itself with siblings like fitune_type or fitune_read.

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?

'Numbered element' and 'the current page' imply this must follow a read that produced element numbers, but the description never states that prerequisite or says when to prefer click over type/read. Usage is inferable rather than stated.

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