Breezeway MCP

breezeway_open

Open a Breezeway page in your signed-in Cloud Browser to create, assign, comment on, and approve property tasks.

Instructions

Open a Breezeway page in your signed-in Cloud Browser (default https://app.breezeway.io) to work with create, assign, comment on and approve property tasks.

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_open"
  }
}

Input Schema

Name	Required	Description	Default
`url`	No	Page to open. Default: https://app.breezeway.io

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations, the description carries the full disclosure burden, and it does contribute one meaningful fact: the browser session is already 'signed-in', so no auth step is needed. It says nothing about what happens on failure, whether an already-open tab is reused, or whether anything is returned, leaving meaningful behavioral gaps.

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 the action first and the default URL immediately after it, which is the right order for a navigational tool. The purpose list at the end is somewhat sprawling but does add usable context, so little is wasted.

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 simple one-parameter, zero-required navigation tool with no output schema, the description covers the essentials: action, target, default destination, and signed-in session state. It omits what the agent should expect after opening (no result value, no indication of what state the page is in), which matters for chaining into click/read/type siblings.

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?

Only one optional parameter exists and schema description coverage is 100%, so the schema already fully documents it. The description merely restates the default URL value, adding no syntax, format, or constraint detail 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?

The description names a specific verb and resource ('Open a Breezeway page') and implicitly scopes it to navigation, which separates it in spirit from interaction siblings like breezeway_click, breezeway_type and breezeway_read. It does not explicitly contrast itself with any sibling, which keeps it short of 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?

The trailing clause ('to work with create, assign, comment on and approve property tasks') hints at the workflow this enables, so a reader can infer it is the entry point before interacting. However, there is no explicit when-to-use statement, no prerequisites, and no named alternative for cases where the page is already open.

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

Deploy Server