Breezeway MCP

breezeway_read

Read the current Breezeway page's text, numbered buttons, links, and fields, optionally within one element, to inspect the signed-in account interface.

Instructions

Read the current Breezeway 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": "breezeway_read"
  }
}

Input Schema

Name	Required	Description	Default
`element`	No	Read only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses the shape of the return content and the existence of a numbering scheme for buttons, which is genuinely useful, but it says nothing about read-only semantics, whether 'current' means the active tab/page, truncation on large pages, or how the numbering can be reused when clicking.

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?

A single front-loaded sentence with no filler; the verb, scope, and returned content types all appear immediately.

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 inspection tool with no output schema, the description covers the essential outcome (page text plus numbered interactive elements). It falls short only on the element-scoping parameter and the semantics of the numbering, which an agent needs in order to chain a follow-up click.

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 'element' parameter and its minimum are already fully documented structurally. The description mentions 'current page' but never explains the scoping parameter or how element indices relate to the numbered elements returned, so it adds no meaning beyond the schema.

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?

States a specific verb and resource ('Read the current Breezeway page') and enumerates the returned content types (text, numbered buttons, links, fields), which clearly frames it as a non-mutating inspection tool. It does not explicitly contrast itself with the action siblings (click, type, open), so sibling differentiation is only implied.

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 implied rather than stated: reading 'the current page' suggests inspecting state before acting, but the description never says when to prefer this over other page-related tools or note any prerequisite such as the page being loaded. No exclusions or alternatives are given.

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

Deploy Server