Skip to main content
Glama

Risk Mitigation Value

bpj_risk_mitigation_value
Read-onlyIdempotent

Compare expected loss before and after mitigation and subtract the cost of taking the action.

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": {
      "probability": "<probability>",
      "impact": "<impact>",
      "mitigated": "<mitigated>",
      "prevention": "<prevention>"
    },
    "name": "bpj_risk_mitigation_value"
  }
}

Input Schema

NameRequiredDescriptionDefault
impactYes
mitigatedYes
preventionYes
probabilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds that the operation is a pure comparison/subtraction with no side effects, but says nothing about units, rounding, sign conventions, or error behavior when inputs are out of range. Some added value, but thin beyond the annotations.

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 padding or redundancy. It is efficient, though it packs two operations (compare, subtract) into one clause without breaking out the formula for clarity.

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 4-parameter pure calculator with no output schema, the description should clarify the return value (a currency amount, presumably) and the interaction of the four inputs. It explains the arithmetic concept but leaves the result type and edge-case behavior implicit.

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%, but each property carries a title (e.g. 'Risk probability (%)', 'Mitigation expense') that supplies basic meaning. The description conveys the underlying formula—probability times impact as expected loss, mitigated probability as post-mitigation loss, minus prevention cost—which lets an agent map all four parameters, though it never names them or states units and output currency explicitly.

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 names a specific computation: it compares expected loss before and after mitigation and subtracts the action cost. That is a concrete verb-plus-resource statement an agent can match to a risk-value calculation, though it does not contrast itself with the many other bpj_* value calculators.

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 guidance on when to use this tool versus alternatives, no stated prerequisites, and no exclusions. The agent must infer from the name and description alone that this is the correct calculator for mitigation ROI rather than, say, a plain expected-value tool.

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.