Skip to main content
Glama

Size a Bloom filter

bpj_system_bloom_size
Read-onlyIdempotent

Calculate Bloom filter bits and an approximately optimal hash count from item count and false-positive target.

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": {
      "items": "<items>",
      "falsePositive": "<falsePositive>"
    },
    "name": "bpj_system_bloom_size"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsYes
falsePositiveYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

The annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds one genuinely useful trait, that the hash count is 'approximately optimal' (i.e., a heuristic result, not an optimum), but says nothing about precision, rounding, or what the returned values look like.

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?

One front-loaded sentence with zero filler that names the computation and both inputs. Nothing could be cut without losing information.

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 two-parameter arithmetic calculator with no output schema, the description covers inputs and named outputs (bits and hash count) adequately. A brief note on output shape or on how extreme false-positive values are treated would close the remaining gap.

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 0% (only titles), so the description must carry meaning, and it does map 'item count' to items and 'false-positive target' to falsePositive. However, it adds nothing beyond those titles: it does not explain that falsePositive is a probability on (0,1) rather than a percentage, nor what units the bounds imply.

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?

A specific verb ('Calculate') and resource ('Bloom filter bits and an approximately optimal hash count'), with the two driving inputs named. It clearly reads as a sizing calculator distinct from the availability/capacity siblings, though it does not explicitly contrast itself with any of 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 only implied: the phrasing 'from item count and false-positive target' tells an agent the preconditions for calling it, but there is no statement of when to prefer this over a related sizing tool, and no exclusions or notes on invalid inputs.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.