Bloom MCP

bloom_click

Clicks a numbered element on the current Bloom page to interact with page controls and continue a task.

Instructions

Click a numbered element on the current Bloom 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>"
    },
    "name": "bloom_click"
  }
}

Input Schema

Name	Required	Description	Default
`element`	Yes	Element number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.1.0Nov 13, 2026

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 does not meet it. It says nothing about what clicking actually causes (navigation, form submission, DOM changes), whether the call waits for a result, or what happens if the element number is stale or no longer present.

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?

A single front-loaded sentence with no filler or redundancy. It is efficient, though so terse that it conveys no structure beyond the bare action.

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?

For a browser-mutating action with zero annotations and no output schema, the definition should explain side effects, failure modes, and what the caller gets back. None of that is present, leaving critical gaps for an agent driving a live page.

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 coverage is 100%, so the 'element' parameter is already fully documented including its minimum and origin ('Element number from the last read'). The description's phrase 'numbered element' adds only marginal reinforcement of that meaning.

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?

The description names a specific verb (click) and a specific resource (a numbered element on the current Bloom page), which is clearly distinct from read/type/open siblings. It stops short of explicitly saying how it differs from bloom_read or bloom_type, but the action itself is unambiguous.

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 when-to-use or when-not-to-use guidance, and no alternative is named. The only sequencing hint ('from the last read') lives in the schema rather than the description, so an agent must infer that bloom_read should precede this call.

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

Deploy Server