Skip to main content
Glama

Warranty Accrual Estimate

bpj_warranty_accrual_estimate
Read-onlyIdempotent

Estimate expected claim count and warranty expense using the sales cohort, claim incidence and average repair cost.

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": {
      "actualQty": "<actualQty>",
      "claims": "<claims>",
      "repair": "<repair>"
    },
    "name": "bpj_warranty_accrual_estimate"
  }
}

Input Schema

NameRequiredDescriptionDefault
claimsYes
repairYes
actualQtyYes

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, idempotentHint, non-destructive and closed-world, so the safety profile is covered and only the computation semantics remain. The description confirms it is a pure estimation over supplied inputs, but says nothing about the formula, rounding, currency of the expense figure, or determinism beyond what idempotentHint implies.

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 well-formed sentence with the outputs and the driving inputs front-loaded and no filler. It could have used a second short clause for units or return shape, but nothing present is wasteful.

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 three-parameter pure calculation with no output schema, the description names the two results but not how they are returned (field names, whether expense is currency-denominated, or how claim count is derived). Adequate to call the tool, but an agent would be guessing at the response shape.

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 description must carry weight; it does partially by mapping 'sales cohort' to actual units, 'claim incidence' to the claim rate, and 'average repair cost' to the mean cost per claim. However it does not confirm units or clarify that claims is expressed as a percentage (0-100) rather than a fraction, leaving that to the schema 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?

Uses a specific verb ('Estimate') with two named outputs ('expected claim count and warranty expense') plus the three driving inputs, so an agent can tell exactly what computation is performed. It lacks any explicit differentiation from siblings, though the domain (warranty accrual) is distinct enough in practice.

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 states what the tool computes but gives no when-to-use guidance, no preconditions (e.g. that the cohort is a policy/accrual period), and no exclusions or alternatives. The agent must infer applicability from the name and inputs alone.

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.