Skip to main content
Glama
Sign In
Breezeway MCP

Breezeway MCP

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

breezeway_type

Types text into a numbered field on the current Breezeway page, using field numbers from the last read to fill task or form inputs.

Instructions

Type text into a numbered field on the current Breezeway page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "element": "<element>",
      "text": "<text>"
    },
    "name": "breezeway_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full behavioral burden and falls well short. It doesn't say whether typing replaces or appends existing field content, whether input/submit events fire, or what state the page is left in. For a browser-automation mutation, those are the details an agent needs.

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 zero filler and the resource scoped immediately. Nothing is redundant or buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema and no annotations, so the description must supply context and doesn't. It omits the read-before-type dependency, replace-vs-append behavior, and any indication of what happens after typing, leaving a 2-param automation tool under-explained.

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%, so both parameters ('text' and 'element') are already documented. The description adds only the framing that 'element' refers to a field on the current page, which is marginal beyond the schema's 'Field number from the last read'.

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 plus resource: "Type text into a numbered field on the current Breezeway page." That cleanly separates typing from siblings like breezeway_click or breezeway_read, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

No when-to-use or prerequisite guidance. The critical precondition — that field numbers come from a prior breezeway_read — is only hinted at by the schema's "Field number from the last read," not stated in the description. Nothing tells the agent whether typing submits the form or requires a follow-up call.

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

Deploy Server

Other Tools