Skip to main content
Glama

Cash For My Note Calculators

Note seasoning calculator

seasoning
Read-onlyIdempotent

A note's seasoning is how long the borrower has been paying, counted from the first payment due date, and this tool gives the months seasoned and the payments due so far. If given payments made, it shows how many were missed or paid ahead, which helps tell a performing note from a non-performing one. Estimates, not offers or appraisals. CashForMyNote.com does not buy notes or make offers.

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": {
      "first_payment_date": "<first_payment_date>",
      "as_of": "<as_of>"
    },
    "name": "seasoning"
  }
}

Input Schema

NameRequiredDescriptionDefault
as_ofYesYYYY-MM-DD
payments_madeNoPayments actually received (optional).
first_payment_dateYesYYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), yet the description still adds real context: how seasoning is computed, what the returned months/payments-due figures mean, and that results are estimates rather than offers or appraisals. It omits error behavior for a first_payment_date after as_of, but the added value is genuine.

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 front-loaded with the definition of seasoning before the outputs and inputs, which is the right order for an agent. The closing disclaimer about CashForMyNote.com not buying notes is boilerplate but short and arguably relevant to how results should be presented.

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

Completeness4/5

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

With only three simple parameters, no output schema, and full annotation coverage, the description supplies enough: calculation basis, outputs, and the role of the optional payments_made. Nothing critical to invoking it correctly is missing, though edge-case handling is unaddressed.

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 coverage is 100%, so the baseline is 3; the description does clarify the semantic effect of the optional payments_made input (computing missed or paid-ahead counts). It adds little about as_of or the date-format expectations beyond what the schema already states.

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 defines seasoning concretely (time since first payment due date) and states the two outputs (months seasoned, payments due). That is a specific verb-plus-resource framing that an agent can distinguish from yield/price/balance siblings, though it never names an alternative tool explicitly.

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 mention that missed/paid-ahead payments 'helps tell a performing note from a non-performing one' hints at when this tool matters. There is no explicit when-to-use, when-not-to-use, or routing to sibling calculators such as note_yield or remaining_balance.

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