CMD+RVL Receipts

Verify loan ending balance (alias)

verify_ending_balance

Read-onlyIdempotent

Alias for verify_loan_field with field='ending_balance': a loan's trust-level SCHEDULED ending balance, current period. Prefer verify_loan_field.

Input Schema

Name	Required	Description
`deal`	Yes	Deal name or alias, e.g. 'WFCM 2020-C58' or 'Wells Fargo 2020-C58'.
`loan_id`	Yes	Loan / entity id within the deal, e.g. '25'.
`claimed_value`	No	Claim to receipt. Required: no claim = refusal, no value.

Output Schema

Name	Required	Description
`as_of`	Yes
`claim`	Yes	Adjudication: claimed_value, tolerance_*, within_tolerance, rationale.
`message`	Yes
`receipt`	Yes	sf-receipt 0.3; schema https://cmdrvl.com/schemas/sf-receipt/v0/schema.json; context https://cmdrvl.com/contexts/obs-receipt/v0/context.json
`claim_verdict`	Yes	Caller-claim verdict; DENY only here.
`resolved_deal`	Yes	Deal resolution: matched, id, cik, candidates.

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedNov 2, 2026

changedOutput schema / properties / claim / additionalProperties
```
Previous value: -falseNew value: +true
```

changedOutput schema / properties / claim / description

Previous value: -"Claim-adjudication detail."New value: +"Adjudication: claimed_value, tolerance_*, within_tolerance, rationale."

removedOutput schema / properties / claim / properties / abs_diff

Removed value: -{
-  "type": [
-    "number",
-    "null"
-  ]
-}

removedOutput schema / properties / claim / properties / basis

Removed value: -{
-  "anyOf": [
-    {
-      "$ref": "#/properties/claim/properties/claimed_value/anyOf/0"
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedOutput schema / properties / claim / properties / claimed_basis
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
removedOutput schema / properties / claim / properties / claimed_unit
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```

removedOutput schema / properties / claim / properties / claimed_value

Removed value: -{
-  "anyOf": [
-    {
-      "type": [
-        "number",
-        "string"
-      ]
-    },
-    {
-      "type": "null"
-    }
-  ]
-}

removedOutput schema / properties / claim / properties / claimed_value_date
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
removedOutput schema / properties / claim / properties / rationale
```
Removed value: -{
-  "type": "string"
-}
```
removedOutput schema / properties / claim / properties / rel_bps_diff
```
Removed value: -{
-  "type": [
-    "number",
-    "null"
-  ]
-}
```
removedOutput schema / properties / claim / properties / tolerance_kind
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
removedOutput schema / properties / claim / properties / tolerance_used
```
Removed value: -{
-  "type": [
-    "number",
-    "null"
-  ]
-}
```
removedOutput schema / properties / claim / properties / within_tolerance
```
Removed value: -{
-  "type": [
-    "boolean",
-    "null"
-  ]
-}
```

removedOutput schema / properties / claim / required

Removed value: -[
-  "claimed_value",
-  "tolerance_kind",
-  "tolerance_used",
-  "abs_diff",
-  "rel_bps_diff",
-  "within_tolerance",
-  "basis",
-  "rationale"
-]

changedOutput schema / properties / resolved_deal / additionalProperties
```
Previous value: -falseNew value: +true
```

addedOutput schema / properties / resolved_deal / description

Added value: +"Deal resolution: matched, id, cik, candidates."

removedOutput schema / properties / resolved_deal / properties / candidates

Removed value: -{
-  "description": "Suggested deal ids when unmatched/ambiguous.",
-  "items": {
-    "type": "string"
-  },
-  "type": "array"
-}

removedOutput schema / properties / resolved_deal / properties / cik

Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / resolved_deal / properties / id

Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}

removedOutput schema / properties / resolved_deal / properties / matched
```
Removed value: -{
-  "type": "boolean"
-}
```
removedOutput schema / properties / resolved_deal / properties / name
```
Removed value: -{
-  "type": [
-    "string",
-    "null"
-  ]
-}
```
removedOutput schema / properties / resolved_deal / properties / query
```
Removed value: -{
-  "type": "string"
-}
```

removedOutput schema / properties / resolved_deal / required

Removed value: -[
-  "query",
-  "matched",
-  "id",
-  "name",
-  "cik",
-  "candidates"
-]

First observedNov 2, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already cover read-only, idempotent, closed-world behavior, so the bar is lower; the description still adds the meaningful qualifier that the balance is SCHEDULED (not actual) and scoped to the current period. It does not restate the refusal-on-no-claim behavior that lives in the schema, but that is already covered there.

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?

A single sentence, front-loaded with the alias equivalence and followed by the field's meaning and the sibling preference. Nothing is redundant.

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?

An output schema exists so return values needn't be explained, and all three parameters are documented in the schema. The only gap is why the alias exists and when it should still be used rather than the canonical tool.

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 description coverage is 100%, so deal, loan_id, and claimed_value are fully documented in the schema, including the 'no claim = refusal, no value' rule. The description adds no parameter-level detail beyond the implicit field='ending_balance', so the baseline of 3 applies.

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 description states exactly what the tool verifies (a loan's trust-level SCHEDULED ending balance for the current period) and identifies itself as an alias for verify_loan_field with field='ending_balance'. That mapping makes it unambiguous against every sibling, including the parent tool.

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

Usage Guidelines4/5

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

"Prefer verify_loan_field" gives explicit routing away from this tool, which is the key selection decision. It stops short of saying when this alias is still appropriate (e.g. legacy callers), so the exclusion is one-sided rather than a full when/when-not rule.

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

All CMD+RVL Receipts 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.