Bloom MCP Server and API by Cotlet

Send contract in Bloom

bloom_send_contract

Read-onlyIdempotent

Send contract 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_contract"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly=true, idempotent=true and non-destructive, and the description reinforces rather than contradicts them with 'opens nothing by itself'. It adds real value beyond the annotations by explaining why browser automation is required (no public Bloom API, Zapier-only integration) and by describing the return shape (screens, buttons, fields). It stops short of stating prerequisites such as being logged in or how long the returned guide will be.

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 the core behavior and the negative scope ('opens nothing by itself') before the connector details. The closing sentence on Bloom's missing public API is slightly tangential and reads like provenance metadata, but it earns its place by steering an agent away from a nonexistent REST path.

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

Completeness5/5

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

For a zero-parameter, read-only guidance tool with no output schema, the description covers what it returns, what it does not do, and which tools carry out the actual work. Nothing an agent needs in order to call it correctly and act on the result is missing.

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 no parameters and the schema is fully closed (additionalProperties: false), so there is no parameter meaning to add. Baseline 4 applies.

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 ('Send contract in the user's own Bloom account') and immediately qualifies it: the tool returns step-by-step instructions rather than performing the send. That qualification is essential, because the name implies an action the tool does not take, and the description resolves the ambiguity in the first two sentences.

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?

Gives explicit sequencing: call this first to get the steps, then execute them with the cotlet_browser_* tools in the Bloom Cloud Browser. It does not state when to prefer the sibling cotlet_app_guide over this tool, which is the one routing gap.

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?