defrr

Reprice a renewal

defrr_reprice_renewal

Use when a renewal was priced too high and needs a credit. Returns the credit note, the revenue to reverse for months already closed, and the corrected revenue month by month. Costs 2 credits (refunded if it fails).

Input Schema

Name	Required	Description
`schedule`	Yes	The contract's terms. The first term needs a startDate; each later term (a renewal) starts the day after the previous one ends when endDateIncluded is true (the default), or on the day the previous one ends when it is false.
`termIndex`	Yes	Which term: 1 is the first renewal, 2 the second, and so on. Only the latest renewal can be corrected for now, so give the position of the last term.
`lockedThrough`	No	The latest month already closed for changes, as YYYY-MM. Revenue in that month and earlier cannot be changed, so the correction is posted in the next month. Leave out or null if no month is closed.
`correctedPrice`	Yes	What the renewal should have cost, in the schedule's currency. Must be lower than its current price.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 31, 2026

changedInput schema / properties / schedule / properties / terms / items / properties / price / description

Previous value: -"The term's total price."New value: +"The term's total price: for all its units, not per unit."

addedInput schema / properties / schedule / properties / terms / items / properties / quantity

Added value: +{
+  "description": "Optional: how many units (seats) the term's total price covers, 1 if you leave it out. It doesn't change the schedule, which follows the total; it is recorded with the contract so its unit price can be seen.",
+  "minimum": 1,
+  "type": "integer"
+}

Changed4 schema fields changedOct 28, 2026

changedInput schema / properties / correctedPrice / description

Previous value: -"What the renewal should have cost. Must be lower than its current price."New value: +"What the renewal should have cost, in the schedule's currency. Must be lower than its current price."

addedInput schema / properties / schedule / properties / currency

Added value: +{
+  "description": "Only for a contract priced in a foreign currency: its code, such as EUR. Every term's price is then in that currency, and each term needs an exchangeRate.",
+  "pattern": "^[A-Za-z]{3}$",
+  "type": "string"
+}

addedInput schema / properties / schedule / properties / exchangeRate

Added value: +{
+  "description": "With currency: the rate for every term that has none of its own.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

addedInput schema / properties / schedule / properties / terms / items / properties / exchangeRate

Added value: +{
+  "description": "With currency: how much of your base currency ONE unit of the foreign currency was worth when this term was booked. Corrections use it, so they agree with what was billed.",
+  "exclusiveMinimum": 0,
+  "type": "number"
+}

Changed2 schema fields changedOct 28, 2026

changedInput schema / properties / schedule / description

Previous value: -"The contract's terms. The first term needs a startDate; each later term (a renewal) starts the day after the previous one ends when endDateIncluded is true, or on the day the previous one ends when it is false."New value: +"The contract's terms. The first term needs a startDate; each later term (a renewal) starts the day after the previous one ends when endDateIncluded is true (the default), or on the day the previous one ends when it is false."

changedInput schema / properties / schedule / properties / endDateIncluded / description

Previous value: -"True if a term's end date is its last day (a 1 Jan to 31 Dec term). False if the end date is the first day of the next term. Defaults to false, so for a new contract send true with the last day the customer is covered (a year from 1 Mar 2026 is endDate 2027-02-28)."New value: +"Always send it. True if a term's end date is its last day (a year from 1 Mar 2026 ends 2027-02-28): use true unless the user's own dates show otherwise. False if the end date is the first day of the next term, as when the user gives the same calendar day a whole number of months later (10 Feb 2027 to 10 Feb 2028, so the last covered day is 9 Feb 2028). Defaults to true if left out."

Changed1 schema field changedOct 28, 2026

changedInput schema / properties / schedule / properties / endDateIncluded / description

Previous value: -"True if a term's end date is its last day (a 1 Jan to 31 Dec term). False if the end date is the first day of the next term. Defaults to false."New value: +"True if a term's end date is its last day (a 1 Jan to 31 Dec term). False if the end date is the first day of the next term. Defaults to false, so for a new contract send true with the last day the customer is covered (a year from 1 Mar 2026 is endDate 2027-02-28)."

First observedOct 20, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description provides critical behavioral context beyond the annotations or schema. It discloses the operational cost (2 credits) and a recovery mechanism (refund if it fails), which are essential for risk-aware agent behavior. It also details the multi-part return structure (credit note, reversals, corrected revenue).

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 definition is highly concise. The most critical information—the use case, output, and transaction cost—is packed into two sentences, front-loading the utility and risks.

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

Completeness5/5

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

Given the complexity of the input schedule and the transactional nature of the tool, the description is remarkably complete. It addresses the required inputs, the cost/risk (2 credits), and the detailed output, making it robust even without a specific output schema provided.

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?

With 100% schema coverage, the baseline is 3. The description confirms the necessity of a reduced price but does not add semantic meaning to the parameters themselves that isn't already documented in the detailed input schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The purpose is extremely clear, defining the specific scenario: when a renewal was priced too high and requires a credit. By focusing on 'renewal' and the 'credit' necessity, it effectively differentiates itself from sibling tools like defrr_reprice_contract.

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

Usage Guidelines5/5

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

It provides explicit usage criteria by stating the exact problem it solves ('priced too high and needs a credit'). This eliminates ambiguity and directs the agent immediately to this tool over general repricing or cancellation tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All defrr tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Reprice a renewal

Input Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources