CMD+RVL Receipts

Verify issuance appraised value

verify_appraised_value

Read-onlyIdempotent

Verify issuance appraised value (Annex A vs ABS-EE). Date/basis mismatches return DATE_INCOMMENSURATE or BASIS_INCOMMENSURATE, not CONFLICT/DENY. Until upstream shards exist, returns UNVERIFIED.

Input Schema

Name	Required	Description
`deal`	Yes	Deal name or alias, e.g. 'WFCM 2020-C58'.
`loan_id`	Yes	Loan / entity id within the deal, e.g. '25'.
`claimed_basis`	No	Optional valuation basis.
`claimed_value`	No	Claim to receipt. Required.
`claimed_value_date`	No	Optional valuation date.

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

A3.7/5.0

Behavior4/5

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

Annotations already cover the read-only/idempotent/closed-world profile, and the description adds genuinely non-obvious behavioral context: date or basis mismatches yield DATE_INCOMMENSURATE/BASIS_INCOMMENSURATE rather than CONFLICT/DENY, and results are UNVERIFIED until upstream shards exist. It does not explain what a CONFLICT/DENY outcome implies or what triggers it.

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?

Three short sentences, purpose front-loaded, followed by result-code caveats and availability status. Dense and mostly waste-free, though the DATE_INCOMMENSURATE/BASIS_INCOMMENSURATE vs CONFLICT/DENY contrast is compressed without explaining the latter terms.

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 an output schema, full schema coverage, and annotations present, the description covers the essentials: what is compared, how mismatch outcomes are classified, and that results are currently UNVERIFIED. Domain terms (Annex A, ABS-EE) and sibling routing are left unexplained, which is a minor gap.

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 the schema already documents deal, loan_id, claimed_basis, claimed_value, and claimed_value_date; baseline 3 applies. The description adds no parameter-level meaning, and it does not resolve the schema's ambiguity where claimed_value is labeled 'Required.' but is absent from the required array.

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?

States the specific verb (verify) and resource (issuance appraised value) and names both data sources being reconciled (Annex A vs ABS-EE), which distinguishes it from generic siblings like verify_loan_field or verify_deal_field. It stops short of explicitly routing the agent away from any particular sibling.

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 by the resource ('verify issuance appraised value') and the 'Until upstream shards exist, returns UNVERIFIED' note usefully signals the tool is currently a no-op for real data. However, there is no explicit when-to-use/when-not guidance and no named alternative for verifying other loan attributes.

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.