Skip to main content
Glama

Independent replica availability

bpj_system_replica_availability
Read-onlyIdempotent

Compute the chance of at least one healthy replica under identical independent failures.

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>"
    },
    "name": "bpj_system_replica_availability"
  }
}

Input Schema

NameRequiredDescriptionDefault
replicasYes
availabilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so safety is covered. The description adds the modeling assumption (independent, identical failure probability), which matters for trusting the result, but says nothing about the output range or format, so it adds only partial behavioral context.

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?

A single sentence with no filler, front-loading the verb and the computed quantity, and folding the key assumption into the same clause. Nothing in it is redundant with the name or title.

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 two-parameter pure calculator with annotations and no output schema, the description is close to sufficient, but it never states that the result is a probability fraction in [0,1] nor ties itself explicitly to the independence-model family it belongs to. Those omissions leave a small but real gap for an agent picking among many availability tools.

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%, so the burden falls on the description, which supplies the meaning of both parameters: 'replicas' as the count of healthy candidates and 'availability' as the per-replica (identical) success fraction. It does not restate the 0-1 bounds or the integer type, but the semantic gloss on 'individual availability fraction' is genuine added value beyond the bare 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?

Names a specific computation (probability of at least one healthy replica) with the governing model (identical, independent failures), which distinguishes it from quorum or serial availability models without naming them. It stops short of explicitly pointing at the sibling tools, which is the only reason it is not a 5.

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 implied rather than stated: 'identical independent failures' signals the regime in which the formula applies, but the description never says when to choose this over bpj_system_quorum_availability or bpj_system_serial_availability, nor any prerequisites. An agent must infer the applicability conditions from the phrase 'independent'.

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.