Breezeway MCP Server and API by Cotlet

Add task comment in Breezeway

breezeway_add_task_comment

Read-onlyIdempotent

Add task comment in the user's own Breezeway account from ChatGPT, Claude or any AI agent. Returns how to do it in Breezeway step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Breezeway Cloud Browser. Breezeway's official API: Breezeway has a REST API for properties, reservations, tasks and people, but you need API keys from a request form, and it has no official MCP server (checked 20 Oct 2026).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The readOnlyHint=true annotation is consistent with the statement that it 'opens nothing by itself', so no contradiction. Beyond the annotations, it discloses the actual return shape (screens, buttons, fields) and the prerequisite context that Breezeway's official API needs request-form API keys and has no MCP server.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core instruction is front-loaded, but the closing sentence about Breezeway's API and MCP status is tangential marketing/context that does not help an agent select or invoke the tool. Phrasing like 'from ChatGPT, Claude or any AI agent' adds words without decision value.

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?

With no parameters, no output schema, and read-only annotations, the definition covers what an agent needs: what the call returns and which sibling tools carry out the actual action. The only shortfall is the absence of explicit routing versus the generic app-guide sibling.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the schema carries no semantics to supplement and the baseline is 4. The description correctly implies no input is required to obtain the guidance.

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 ('Add task comment') scoped to the user's own Breezeway account, and clarifies the tool itself only returns step-by-step instructions rather than performing the write. It does not explicitly distinguish itself from nearby siblings like cotlet_app_guide, so it stops 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context: call this to get the click-by-click procedure, then execute it with the cotlet_browser_* tools in the user's Breezeway Cloud Browser. It does not spell out when-not-to-use or contrast with cotlet_app_guide, which is the main gap.

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

All Breezeway MCP Server and API by Cotlet tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?