Skip to main content
Glama

breely_read

Reads the current Breely page’s text and numbered buttons, links, and fields, optionally limited to one element, so AI agents can inspect page content before acting.

Instructions

Read the current Breely 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": "breely_read"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full disclosure burden. It does useful work by listing the returned content (text, numbered buttons, links, fields), which tells the agent that elements are numbered and therefore referenceable by later actions. It says nothing about whether reading has any side effects, how large pages are handled, or whether the snapshot can go stale.

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 front-loaded sentence that states the verb, the target, and the returned contents with no filler. Nothing is redundant or buried.

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 read tool with no output schema, the description covers purpose and returned content adequately, and the parameter is fully documented in the schema. The only meaningful gap is how the numbering exposed by this tool maps onto the sibling click/type tools.

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 single optional `element` parameter is documented in the schema as "Read only inside this element." The description adds no additional meaning about scoping, element numbering, or how the scope interacts with the returned numbering, so the schema baseline of 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 ("Read") and resource ("the current Breely page") and even enumerates what comes back: text, numbered buttons, links and fields. That is enough to separate it from breely_click/breely_type/breely_open without opening any schema. It stops short of naming a sibling or stating an explicit contrast, which keeps it from a 5.

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?

"Current Breely page" implies the tool applies to whatever page is active, which is a usable cue when deciding between this and breely_open or breely_close. However, there is no explicit when-to-use statement, no mention of when not to use it, and no pointer to alternatives such as breely_status or breely_guide for page metadata.

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