Skip to main content
Glama

Quorum availability

bpj_system_quorum_availability
Read-onlyIdempotent

Compute the binomial probability of having at least the required number of healthy replicas.

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": {
      "availability": "<availability>",
      "replicas": "<replicas>",
      "required": "<required>"
    },
    "name": "bpj_system_quorum_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
replicasYes
requiredYes
availabilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds that this is a pure binomial computation, which signals a deterministic, side-effect-free calculation, but it says nothing about the independence assumption or the scale/interpretation of the result.

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 or redundant restatement of the title. It is tight, though brevity here edges toward under-specification.

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

Completeness2/5

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

With no output schema, the description should say that the tool returns a probability in [0,1] and note the underlying independence assumption. For a three-required-parameter computation with zero schema coverage, the definition leaves too much for the agent to infer.

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

Parameters2/5

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

Schema description coverage is 0% and the parameters carry only bare titles ('Total replicas', 'Required healthy replicas', 'Individual availability fraction'). The description reinforces the replicas/required concepts but never clarifies that 'availability' is a per-replica fraction in [0,1] or how the three inputs combine, leaving the semantics largely to the titles.

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 ('Compute') and a specific resource ('binomial probability of having at least the required number of healthy replicas'), which is enough to know it is a quorum math tool. It does not differentiate itself from nearby siblings such as bpj_system_replica_availability or bpj_system_serial_availability, so an agent must guess which of the availability calculators fits.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites, and no named alternative for the closely related availability tools. Usage can only be inferred from the tool name and the phrase 'required number of healthy replicas'.

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.