Bloom MCP

bloom_open

Open a Bloom page in your signed-in Cloud Browser to manage client bookings, invoices, and contracts, defaulting to https://app.bloom.io.

Instructions

Open a Bloom page in your signed-in Cloud Browser (default https://app.bloom.io) to work with manage client bookings, invoices and contracts.

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": "bloom_open"
  }
}

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden, and it does disclose one useful trait: the page opens inside the user's signed-in Cloud Browser session, so authentication is implicit. It does not say what happens to the currently open page, whether it waits for load, or how failures surface.

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?

It is a single front-loaded sentence with no padding, which is good. However, the malformed phrase 'to work with manage' is a real grammatical error that forces the reader to reparse the sentence instead of clarifying intent.

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 one-optional-parameter navigation tool with no output schema and no annotations, the description covers the essentials: what it opens, where, and in what session. It stops short of describing post-navigation behavior or failure modes, which leaves an agent guessing about follow-up steps.

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% and the single 'url' parameter is already documented with its default, so the description merely repeats the default URL. Baseline 3 applies since the schema does the heavy lifting and no extra syntax or filtering meaning is added.

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: 'Open a Bloom page in your signed-in Cloud Browser', with a concrete default target (https://app.bloom.io). The purpose is unambiguous, though the trailing clause is garbled ('to work with manage client bookings, invoices and contracts'), which blunts the explanation of why one would open the page.

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?

There is no explicit guidance on when to use this versus siblings like bloom_read, bloom_status, or bloom_click, nor any stated prerequisite or sequencing rule. The mention of a 'signed-in Cloud Browser' implies an authenticated session already exists, but the agent must infer that navigation is the first step.

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

Deploy Server