Skip to main content
Glama

BRAINIAC Accounts Payable

Calculate a payment due date

accounts-payable_payment-due-date-calculate

Return a stated due date, or calculate one from an invoice date plus terms that were actually stated. Net 30 is not assumed, and no payment is scheduled. Price $0.03 USDC. POST /api/v1/accounts-payable/payment-due-date-calculate. Unpaid calls return 402 and do not run.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "accounts-payable_payment-due-date-calculate"
  }
}

Input Schema

NameRequiredDescriptionDefault
fileNo
invoiceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does real work: it declares the tool is non-mutating ('no payment is scheduled'), states it will not fabricate Net 30 defaults, discloses cost ($0.03 USDC), and names the failure mode (402 on unpaid calls, which do not run). It omits output shape and what happens on ambiguous or missing terms.

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?

Front-loaded and tight: the core behavior and the 'Net 30 is not assumed' caveat come first, followed by cost and transport details. The raw 'POST /api/v1/accounts-payable/payment-due-date-calculate' is largely redundant with the name but does confirm transport. No filler sentences.

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 tool with a deeply nested two-object schema, no annotations, and no output schema, the description covers economics and failure modes well but leaves the file-vs-invoice input choice and the returned value unexplained. It is adequate to attempt a call but not to call it optimally.

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% across two nested object parameters. The description only indirectly gestures at invoice.invoiceDate and invoice.paymentTerms; the entire `file` parameter (PDF/CSV/base64 upload) is never mentioned, nor is any precedence rule when both file and invoice are supplied. An agent would not learn from this text that it can upload a document instead of structured invoice data.

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 verb+resource: return a stated payment due date or compute one from invoice date plus stated terms. That is far more precise than the bare name, and the phrase 'terms that were actually stated' implicitly separates it from a terms-extraction sibling. It stops short of explicitly naming the alternative (e.g. payment-terms-extract) to extract terms first.

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 implied rather than stated: the agent can infer this is the tool to call once invoice date and terms are known, and 'Net 30 is not assumed' signals a constraint on inputs. There is no explicit when-to-use or when-not-to-use guidance, and no statement about whether terms must be extracted by a sibling first.

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.

Resources