Skip to main content
Glama

Single-Period Expected Credit Loss

bpj_single_period_credit_loss
Read-onlyIdempotent

Combine exposure, period probability of default and loss given default into an undiscounted expected loss.

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": {
      "exposure": "<exposure>",
      "probability": "<probability>",
      "severity": "<severity>"
    },
    "name": "bpj_single_period_credit_loss"
  }
}

Input Schema

NameRequiredDescriptionDefault
exposureYes
severityYes
probabilityYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already establish that this is a read-only, idempotent, closed-world, non-destructive calculation. The description adds meaningful context by stating the result is an undiscounted expected loss, but it does not describe output scaling, rounding, or boundary behavior.

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?

The definition is a single efficient sentence with the calculation and result front-loaded. There is no unnecessary wording.

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 three-parameter calculator with rich annotations and schema bounds, the description is adequate but incomplete. It omits the explicit formula and output details, which would help an agent invoke it correctly without relying on inference.

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%, so the description should compensate, but it mainly restates the three input names. It does not specify the formula, percentage handling, or how the inputs are combined into the output, leaving important parameter meaning to the schema titles and constraints.

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 states a specific calculation: combining exposure, period probability of default, and loss given default into an undiscounted expected loss. This is clear enough to distinguish it from unrelated siblings, but it does not explicitly differentiate it from other credit-loss or loss-related tools.

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?

The description explains what the tool computes but gives no guidance on when to use it versus alternatives, nor any exclusions or prerequisites. Usage is only implied by the calculation itself.

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.