Skip to main content
Glama

breely_open

Opens a Breely page in your signed-in Cloud Browser so you can manage bookings, availability, forms, invoices, and client reports.

Instructions

Open a Breely page in your signed-in Cloud Browser (default https://app.breely.com) to work with bookings, availability, forms, invoices and client reports.

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

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://app.breely.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

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 burden; it does disclose that the page loads in a 'signed-in Cloud Browser' and gives the default URL, which is useful behavioral context. It omits whether a new session/tab is created, what happens if the session is unauthenticated, and whether page content is returned or must be fetched separately via breely_read.

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 compact sentence with the action and default front-loaded and no filler. It is efficient, though the trailing list of domain areas is somewhat decorative rather than instructive.

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-optional-parameter tool with no output schema and no annotations, the description covers the core action but leaves the agent guessing about session behavior, error conditions, and the intended follow-up (read/click/type). It is adequate but not fully self-sufficient.

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% and the single optional 'url' parameter is already documented in the schema, including its default. The description merely restates the default URL, adding no format, validation, or navigation semantics beyond the structured field.

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 ('Open') and resource ('a Breely page in your signed-in Cloud Browser') plus the default target URL, which makes the action unambiguous. It is reasonably distinguishable from siblings like breely_close or breely_read by verb alone, but never names those siblings to sharpen the contrast.

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 clause 'to work with bookings, availability, forms, invoices and client reports' hints at the context in which to call it, and 'signed-in' implies an auth prerequisite. However, there is no explicit when-to-use vs when-not guidance, no statement that this should precede breely_click/breely_type/breely_read, and no mention of alternatives.

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