Skip to main content
Glama

Verify a deal's loan-status counts (derived)

verify_loan_status_counts
Read-onlyIdempotent

Verify count claims over loan status ('N in special servicing / paid off / defeased') for a deal. Counts are DERIVED from the ABS-EE tape, not reported by any filing. Three grains, never mixed: activity (active, resolved_paid_off, defeased); servicing: in_special_servicing = loans CURRENTLY with the special servicer (the count for 'N in special servicing'; it OVERLAPS active, never sum); resolution reason (resolved_via_special_servicing and other payoff reasons) = loans that already LEFT the pool, NOT current counts. Pass claimed for exact per-status adjudication. Uncovered deal: UNVERIFIED.

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": {
      "deal": "<deal>"
    },
    "name": "verify_loan_status_counts"
  }
}

Input Schema

NameRequiredDescriptionDefault
dealYesDeal name or alias, e.g. 'WFCM 2020-C58'.
claimedNoOptional claimed per-status counts, e.g. {"in_special_servicing": 10, "defeased": 2}. Each is adjudicated by EXACT match against the derived count.

Output Schema

NameRequiredDescriptionDefault
as_ofYes
messageYes
statusesYesPer status: status, grain, count, claimed, claim_verdict, receipt.
claim_verdictYes
resolved_dealYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / properties / claim_verdict / enum
      Previous value: -[
      -  "CONFIRM",
      -  "DENY",
      -  "CONFLICT",
      -  "UNVERIFIED"
      -]New value: +[
      +  "CONFIRM",
      +  "DENY",
      +  "CONFLICT",
      +  "UNVERIFIED",
      +  "OUT_OF_COVERAGE"
      +]
  2. Changed17 schema fields changed
    • removedOutput schema / properties / as_of / description
      Removed value: -"The as-of period the derived counts describe."
    • removedOutput schema / properties / claim_verdict / description
      Removed value: -"Overall: DENY if any claimed status mismatches; UNVERIFIED if uncovered; else CONFIRM."
    • removedOutput schema / properties / message / description
      Removed value: -"Human-readable summary."
    • changedOutput schema / properties / resolved_deal / additionalProperties
      Previous value: -falseNew value: +true
    • 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"
      -]
    • changedOutput schema / properties / statuses / description
      Previous value: -"One entry per loan-status, each with its DERIVED receipt."New value: +"Per status: status, grain, count, claimed, claim_verdict, receipt."
    • addedOutput schema / properties / statuses / items / $ref
      Added value: +"#/properties/resolved_deal"
    • removedOutput schema / properties / statuses / items / additionalProperties
      Removed value: -false
    • removedOutput schema / properties / statuses / items / properties
      Removed value: -{
      -  "claim_verdict": {
      -    "description": "Exact-match adjudication of `claimed` vs the derived `count` (CONFIRM/DENY/UNVERIFIED).",
      -    "enum": [
      -      "CONFIRM",
      -      "DENY",
      -      "CONFLICT",
      -      "UNVERIFIED"
      -    ],
      -    "type": "string"
      -  },
      -  "claimed": {
      -    "description": "The caller's claimed count for this status, if any.",
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "count": {
      -    "description": "The DERIVED count for this status (null when uncovered).",
      -    "type": [
      -      "number",
      -      "null"
      -    ]
      -  },
      -  "grain": {
      -    "description": "servicing_status (in_special_servicing) is CURRENT and overlaps active; resolution_reason is why a loan LEFT the pool.",
      -    "enum": [
      -      "activity_status",
      -      "servicing_status",
      -      "resolution_reason"
      -    ],
      -    "type": "string"
      -  },
      -  "receipt": {
      -    "additionalProperties": true,
      -    "description": "The per-status DERIVED_UNCONTESTED sf-receipt (derivation citation + derived_from). Canonical JSON Schema: https://cmdrvl.com/schemas/sf-receipt/v0/schema.json",
      -    "properties": {},
      -    "type": "object"
      -  },
      -  "status": {
      -    "description": "Loan-status key (active, defeased, in_special_servicing, …).",
      -    "type": "string"
      -  }
      -}
    • removedOutput schema / properties / statuses / items / required
      Removed value: -[
      -  "status",
      -  "grain",
      -  "count",
      -  "claimed",
      -  "claim_verdict",
      -  "receipt"
      -]
    • removedOutput schema / properties / statuses / items / type
      Removed value: -"object"
  3. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations (which already declare readOnly/idempotent/non-destructive) by disclosing that counts are derived rather than reported, that three grains must never be mixed, and that in_special_servicing OVERLAPS active and must never be summed. It also states the fallback behavior for uncovered deals, covering semantics annotations cannot express.

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-loads the core purpose and keeps every sentence substantive, with no filler. It is dense and telegraphic with heavy capitalization emphasis, which slightly hurts readability but not information density.

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?

For a derivation-heavy verification tool, the description covers the grain model, overlap caveat, adjudication mode, and uncovered-deal outcome, which is everything an agent needs to call it correctly. An output schema exists, so return-value explanation is rightly omitted.

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 `deal` and `claimed` details are already documented in the schema. The description adds real meaning by explaining the grain semantics of the status keys (overlap of in_special_servicing with active; resolution reasons are loans that left the pool), but this is largely restated context rather than parameter-specific syntax, so baseline 3 applies.

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 a specific verb and resource: 'Verify count claims over loan status ... for a deal,' and adds a crucial scoping fact (counts are DERIVED from the ABS-EE tape, not reported by any filing). It does not name which sibling to use instead (e.g., verify_claims or verify_loan_field), so it falls short of a 5.

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?

Explicitly says to pass `claimed` for exact per-status adjudication and documents the uncovered-deal outcome ('UNVERIFIED'), giving clear operating context. It lacks an explicit statement of when NOT to use it or which sibling handles overlapping claim types, so no exclusions.

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.