Skip to main content
Glama
Bloomerang MCP Server

Bloomerang MCP Server

bloomerang_guide

Get guidance on using Bloomerang to manage constituents, gifts, interactions, and duplicate records, including screens and sign-in. Call this first before other actions.

Instructions

How to work in Bloomerang (constituents, gifts, interactions and duplicate records): its screens and the sign-in link. Call this first.

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

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in Bloomerang, in your words.

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 supplied, so the description carries the full burden; it implies a read-only informational response (screens and a sign-in link) but never states whether the tool is side-effect free, what form the guidance takes, or how the answer is scoped to the supplied task. It adds meaningful context about the domain areas covered, which is more than nothing, but leaves the behavioral profile largely implied.

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?

Two short sentences with the domain scope up front and the imperative call-to-action at the end; nothing is wasted. The parenthetical topic list is compact and informative rather than padding.

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 low-complexity, zero-required-parameter guidance tool with no output schema or annotations, the description covers what the tool is, what topics it addresses, and when to invoke it. The only real gap is how the guidance is returned, which is modest given the tool's simplicity.

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% for the single optional 'task' parameter, which is already described as 'What you want done in Bloomerang, in your words.' The description adds no syntax, formatting, or specificity guidance beyond the schema, so the baseline of 3 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?

The description states a specific resource — guidance on working in Bloomerang, covering constituents, gifts, interactions, duplicate records, screens, and the sign-in link — so the agent knows this is a help/orientation tool rather than a data operation. It does not explicitly differentiate itself from any named sibling, relying instead on 'Call this first' to signal its role.

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?

'Call this first' is an explicit sequencing instruction that tells the agent when to reach for this tool before others. There are no when-not conditions or named alternatives, so the guidance is clear but not exhaustive.

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