Skip to main content
Glama

Trade Credit Discount Cost

bpj_trade_credit_discount_cost
Read-onlyIdempotent

Annualize the cost of foregoing an early-payment discount on a simple 365-day basis.

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": {
      "early": "<early>",
      "earlyDay": "<earlyDay>",
      "netDay": "<netDay>"
    },
    "name": "bpj_trade_credit_discount_cost"
  }
}

Input Schema

NameRequiredDescriptionDefault
earlyYes
netDayYes
earlyDayYes

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?

Annotations already establish that this is a read-only, idempotent, non-destructive calculation, so the safety profile is covered. The description adds a useful behavioral assumption by specifying a simple 365-day basis. However, it does not describe edge-case handling, rounding, or the expected return value.

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 description is a single front-loaded sentence with no wasted wording. It states the operation and the calculation basis efficiently.

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 financial calculator, the description gives enough to understand the core purpose and basis. But with no output schema and 0% parameter description coverage, it should do more to explain the day parameters and what result is returned.

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 must compensate by explaining the three parameters. It only implies the meaning of the discount percentage and says nothing about how earlyDay and netDay are interpreted, such as whether days are measured from invoice date. The schema titles help, but the description adds little beyond them.

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 operation: annualizing the cost of foregoing an early-payment discount. It also specifies the 365-day basis, making the calculation method clear. It does not explicitly distinguish this tool from similarly named finance calculators, so it falls short of a 5.

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 gives no explicit guidance on when to use this tool versus alternatives. It implies a trade-credit early-payment context, but does not state exclusions, prerequisites, or which sibling calculator to choose.

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.