Skip to main content
Glama
Bloomerang MCP Server

Bloomerang MCP Server

bloomerang_open

Opens a Bloomerang page in your signed-in Cloud Browser so you can manage constituents, gifts, interactions, and duplicate records.

Instructions

Open a Bloomerang page in your signed-in Cloud Browser (default https://crm.bloomerang.co) to work with constituents, gifts, interactions and duplicate records.

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": "bloomerang_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://crm.bloomerang.co

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden; it does disclose that the browser is already 'signed-in', which tells the agent no separate auth is needed. It says nothing about whether navigation replaces the current page, whether the call waits for load, or what state is lost - all meaningful for a navigation tool with zero annotation coverage.

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; the trailing list of resource types is slightly loose but does real work by telling the agent what kinds of tasks this page supports.

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?

For a one-optional-parameter navigation tool with no output schema, the description covers target, default domain, auth context, and purpose. The only real gap is whether the call returns page content or merely navigates, which matters for sequencing with siblings.

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% and the single optional parameter already documents its own default, so the description adds no format, path, or query-string guidance beyond the schema. Baseline 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 uses a concrete verb and resource ('Open a Bloomerang page'), states the default target (https://crm.bloomerang.co), and names the domain objects of interest (constituents, gifts, interactions, duplicates). It implicitly separates itself from action siblings like bloomerang_click/bloomerang_read by framing this as navigation, but it never explicitly says so.

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: an agent can infer this is the entry step that loads a page before clicking/reading/typing. There is no explicit statement of when to call it (e.g. first call, or when the current page is wrong) and no named alternative or exclusion.

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