Skip to main content
Glama

Invoice Due Date and Early Discount

bpj_invoice_due_date
Read-onlyIdempotent

Apply calendar-day invoice terms and an early-payment discount to calculate deadlines and amounts.

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": {
      "issued": "<issued>",
      "netDays": "<netDays>",
      "discountDays": "<discountDays>",
      "discount": "<discount>",
      "total": "<total>"
    },
    "name": "bpj_invoice_due_date"
  }
}

Input Schema

NameRequiredDescriptionDefault
totalYes
issuedYes
netDaysYes
discountYes
discountDaysYes

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 declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world scope, so safety is covered. The description adds the calendar-day convention, which is real behavioral context, but does not disclose the calculation rule (due date = issued + netDays?), rounding, or what happens when discountDays exceeds netDays.

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 filler, and the key scoping qualifier ("calendar-day") appears early. It is efficient, though brevity tips into under-specification rather than pure economy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a five-parameter numeric calculator with no output schema, so the description should explain at least the shape of the computed result (due date, discounted amount). Instead it explains neither the inputs nor the return values, leaving an agent unable to predict the output.

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 carry parameter meaning, and it does not. It never clarifies how netDays, discountDays, discount, and total combine, nor how discountDays interacts with netDays, leaving only the terse schema titles to guide input.

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?

Names a concrete verb ("Apply ... terms") and resource ("calendar-day invoice terms and an early-payment discount") plus the outcome ("calculate deadlines and amounts"). "Calendar-day" implicitly sets it apart from the business-day sibling, though that sibling is never named.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the "calendar-day" qualifier hints at when this applies versus business-day conventions, but the description never states when to choose this tool over a business-day alternative, nor any prerequisites. No explicit when-not guidance.

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.