Skip to main content
Glama

Failed Delivery Cost

bpj_failed_delivery_cost
Read-onlyIdempotent

Project redelivery costs after first-attempt failures and return-to-sender costs for the share failing again.

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": {
      "shipments": "<shipments>",
      "fail": "<fail>",
      "retryCost": "<retryCost>",
      "returnRate": "<returnRate>",
      "returnCost": "<returnCost>"
    },
    "name": "bpj_failed_delivery_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
failYes
retryCostYes
shipmentsYes
returnCostYes
returnRateYes

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 the tool as read-only, idempotent, non-destructive, and closed-world. The description adds the business calculation context but does not explain the formula, assumptions, precision, or whether the result is a total or a breakdown.

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?

It is a single front-loaded sentence with no wasted preamble. The phrasing is slightly awkward, especially "for the share failing again," but the description remains compact and readable.

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 five-parameter calculation tool with no output schema, the description is adequate but incomplete. It states what is being projected but does not define the return value, formula, or output shape well enough for an agent to know exactly what to expect.

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 the schema titles themselves are fairly descriptive. The description conceptually maps first-attempt failures, redelivery cost, return-to-sender cost, and the share failing again, but it omits shipments/package count and does not clarify how the inputs combine.

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 uses a specific verb, "Project," and names the resources and conditions: redelivery costs after first-attempt failures plus return-to-sender costs. It is clear what the tool calculates, though it does not explicitly distinguish itself from any sibling tool.

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 explicit when-to-use guidance, no when-not-to-use guidance, and no named alternative. The calculation context implies use, but an agent gets no routing or prerequisite information.

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.