Bloom MCP Server and API by Cotlet

Send invoice in Bloom

bloom_send_invoice

Read-onlyIdempotent

Send invoice in the user's own Bloom account from ChatGPT, Claude or any AI agent. Returns how to do it in Bloom step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Bloom Cloud Browser. Bloom's official API: Bloom publishes no public API or developer docs; its only connection is a Zapier app with triggers such as new lead or new payment (checked 8 Nov 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": "bloom_send_invoice"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Goes well beyond the annotations: it discloses that nothing is opened by the tool itself, that the return value is a screen/button/field walkthrough, and that Bloom has no public API (only a Zapier app with trigger-only coverage). That last fact explains why the browser tools are mandatory, which the readOnlyHint alone would not tell an agent.

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?

Front-loaded with what the tool does and does not do, then the follow-up mechanism, then the API caveat. It is dense but every sentence carries decision-relevant information; the parenthetical Zapier trigger examples and the 'checked 8 Nov 2026' stamp are the only mildly expendable details.

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 output schema, the description correctly compensates by describing the shape of the return value (screens, buttons, fields). It does not cover failure or precondition cases such as the user not being signed in to Bloom, which would matter before handing off to browser automation.

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 and the schema is fully closed (additionalProperties: false), so there is nothing for the description to disambiguate. Baseline for a no-parameter tool applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource (send invoice in Bloom) and immediately clarifies the tool's real nature: it returns step-by-step instructions rather than performing the action. It also distinguishes itself from the cotlet_browser_* siblings by naming them as the follow-up execution mechanism, so an agent can place it correctly without opening any schema.

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?

The workflow is clear: call this first, then carry out the steps with cotlet_browser_* in the user's Bloom Cloud Browser. What is missing is explicit routing against the other bloom_* siblings (bloom_record_payment, bloom_send_contract) and against cotlet_app_guide, which an agent could plausibly confuse with this guide-style tool.

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

All Bloom 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?