Skip to main content
Glama

breely_click

Clicks a numbered element on the current Breely page so AI agents can interact with controls using element numbers from the latest read.

Instructions

Click a numbered element on the current Breely 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": "breely_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.1/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. It notes the action targets 'the current Breely page,' hinting at state dependence, but never discloses that clicking can trigger navigation or other side effects, nor that element numbers are only valid until the page changes.

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 front-loaded sentence with zero filler or repetition. It is efficient, though arguably terse to the point of under-specifying a stateful action.

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 an unannotated, side-effecting action tool with no output schema, the definition says nothing about what happens after the click, whether the element reference can go stale, or what a failure looks like. The schema covers the parameter, but the behavioral picture an agent needs is missing.

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 'Element number from the last read' meaning. The description's word 'numbered' merely echoes the schema without adding format or validity rules, so 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 gives a specific verb plus resource: 'Click a numbered element' on 'the current Breely page.' That is clearly distinct from read/type/open/close siblings in intent, though the description itself does not name or contrast any sibling.

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: clicking a 'numbered' element suggests it follows a read that produces element numbers, but the description never states that prerequisite or says when to prefer breely_type over a click. No when-not guidance and no alternatives are named.

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