Skip to main content
Glama

Serial dependency availability

bpj_system_serial_availability
Read-onlyIdempotent

Multiply independent availability terms for a stack in which every dependency is required.

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

Input Schema

NameRequiredDescriptionDefault
availabilityYes
dependenciesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, closed-world, non-destructive behavior, so the description only needs to add operation context. It adds the multiplication concept but does not explain the formula, return value, or edge cases, making a 3 appropriate.

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 no filler, stating the core operation first. It is appropriately sized for a simple two-parameter calculator, even if it is under-informative elsewhere.

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 simple availability calculator, the description states the core operation but omits the exact combination rule (for example, availability raised to the dependencies count) and leaves parameter interpretation to schema titles. With 0% schema description coverage and no output schema, that is a meaningful gap.

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 description provides no parameter-specific meaning: it never clarifies that 'availability' is a 0–1 fraction or that 'dependencies' is a count of identical required components. The schema titles carry some meaning, but the description does not compensate for the coverage gap.

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 operation ('Multiply') and scope ('a stack in which every dependency is required'), which conceptually distinguishes the serial all-required case from redundancy or quorum tools. It stops short of naming any sibling alternative, so a 4 rather than 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?

The phrase 'for a stack in which every dependency is required' supplies an implied use condition, but there is no explicit when-not guidance or comparison to the quorum/replica siblings. That is enough for implied usage, but not clear context plus alternatives.

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.