Skip to main content
Glama
Bloomerang MCP Server

Bloomerang MCP Server

bloomerang_type

Types text into a specified numbered field on the current Bloomerang page, enabling AI agents to fill forms by field index.

Instructions

Type text into a numbered field on the current Bloomerang 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>",
      "text": "<text>"
    },
    "name": "bloomerang_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/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 disclosure burden for a mutating form action, and it says nothing about whether existing text is replaced or appended, whether the value is committed/submitted, whether focus or scrolling changes, or what happens if the field number is stale. Only the implicit assumption of an active page is conveyed.

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?

A single front-loaded sentence with the action verb first and the locating constraint second; nothing is wasted and nothing is buried.

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

Completeness3/5

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

For a two-parameter typing tool with a fully documented schema, the essentials are covered. However, with no annotations and no output schema, the definition should have stated whether the action submits or merely fills, and how stale field indices fail — those gaps matter for an agent driving a form.

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 both parameters are already documented, establishing the baseline of 3. The description contributes only the notion that the field number is scoped to the currently loaded page; it adds no format, length, or failure semantics for 'text' beyond 'Text to type.'

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 — typing text into a numbered field — plus the scope 'on the current Bloomerang page', which separates it from bloomerang_read (fetch page contents) and bloomerang_click (act on an element). It never names a sibling explicitly, so an agent must infer the pairing from the field-numbering convention rather than being told.

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 only implied: 'current page' and 'numbered field' hint that a page must be open and previously read before typing, but the description never states prerequisites or when to prefer this over click/read. There are no exclusions or alternative-routing sentences, so an agent has to reconstruct the workflow from the vocabulary.

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