Skip to main content
Glama
Sign In
Bloom MCP

Bloom MCP

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

bloom_read

Reads all or part of the current Bloom page, including text, numbered buttons, links, and fields, so AI agents can inspect the interface and choose the next action.

Instructions

Read the current Bloom page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, but the verb "Read" and the page-scoped return description make the non-mutating behavior reasonably clear. The description does not disclose permissions, freshness guarantees, output format, or numbering stability, so meaningful behavioral context is still missing.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is a single front-loaded sentence with no wasted wording. It states the action and the returned content efficiently.

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?

This is a low-complexity read tool with one optional parameter and no output schema, and the description supplies enough return-value context for an agent to understand what it gets. Minor details such as output shape or limits are omitted but are not critical here.

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 optional element parameter is fully documented in the schema as a scope restriction. The description adds no parameter guidance beyond that, so the baseline of 3 is appropriate.

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 gives a specific verb, "Read," and a specific resource, "the current Bloom page," then enumerates what is returned: text, numbered buttons, links, and fields. It implicitly distinguishes itself from mutating siblings such as bloom_click and bloom_type, but does not explicitly contrast with them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: the tool reads the current page for inspection, likely before clicking or typing. However, there is no explicit guidance on when to use this versus bloom_status or bloom_guide, and no exclusions are stated.

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

Deploy Server

Other Tools