Skip to main content
Glama
Bloomerang MCP Server

Bloomerang MCP Server

bloomerang_status

Verify that your Cotlet.dev account, available credits, and Bloomerang connection are ready before using Bloomerang tools.

Instructions

Check that your Cotlet.dev account and Bloomerang are ready: account, credits and Bloomerang connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

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 supplied, the description carries the full behavioral burden. It does disclose the three things being verified (account, credits, Bloomerang connection), which is genuine behavioral content, but it says nothing about what happens on failure, whether it mutates anything, or how results are reported.

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 preamble or filler. The colon list slightly restates the earlier 'ready' clause, a minor redundancy, but overall it is tight and readable.

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 zero-parameter, read-only readiness check this is close to sufficient, and the checks performed are named. However, with no output schema, the description leaves the shape of the result (per-check pass/fail vs. a single verdict) entirely unstated, which is the main thing an agent would want to know.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is no parameter semantics for the description to compensate for; the baseline for a parameterless tool applies. Nothing in the description misleads about inputs.

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 ('Check') and a specific subject (Cotlet.dev account readiness, credits, and Bloomerang connection), which is meaningfully distinct from the action-oriented siblings like bloomerang_open or bloomerang_type. It stops short of explicitly contrasting itself with any sibling, but the purpose 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 Guidelines3/5

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

The phrasing 'Check that ... are ready' implies a pre-flight or troubleshooting role, so an agent can infer it should be called before other operations or when something appears broken. There is no explicit statement of when to use it versus alternatives, and no mention of prerequisites or call ordering.

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