Bloom MCP

bloom_guide

Guides you through Bloom's screens and sign-in link so you can manage client bookings, invoices, and contracts; call this first.

Instructions

How to work in Bloom (manage client bookings, invoices and contracts): its screens and the sign-in link. Call this first.

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

Input Schema

Name	Required	Description	Default
`task`	No	What you want done in Bloom, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

TDQS

A3.6/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 discloses the content returned (screens and a sign-in link), which implies a read-only informational call, but never states that it is non-mutating, whether it needs auth, or what the response looks like. It gives some behavioral signal without a full safety or output profile.

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?

Two short clauses plus a directive, with the purpose front-loaded and no filler. The parenthetical scoping is efficient, though "its screens and the sign-in link" is slightly awkward phrasing that could be tightened.

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?

For a one-optional-parameter guide tool with no output schema and no annotations, the description covers what it is, what it contains, and when to call it. Only the shape of the returned guidance is left implicit, which is a minor gap at this complexity.

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 optional "task" parameter is already documented in the schema as free-form intent, so the description adds nothing beyond it. Under the high-coverage baseline this is an adequate 3, though it could have clarified whether the task string steers the guide.

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?

"How to work in Bloom" plus the parenthetical scope (client bookings, invoices, contracts) and the stated payload (screens, sign-in link) make it clear this is an orientation/guide resource rather than an action. It is distinguishable from the action siblings (click, open, read, type, close), though the phrasing is slightly abstract about what the guide actually returns.

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?

"Call this first" is an explicit ordering directive that tells the agent when to reach for this tool relative to everything else. There is no when-not guidance or named alternative, but for an entry-point guide tool the primary usage condition is stated outright.

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

Deploy Server