Skip to main content
Glama

Verify a deal counterparty (roster)

verify_counterparty
Read-onlyIdempotent

Adjudicate 'who is the on deal X' against the SEC 10-D counterparty roster (today: master and special servicer). A SINGLE-SOURCE roster fact. Master is the roster party, NOT the ABS-EE tape's primary servicer. Pass claimed_name: CONFIRM/DENY under the ledger's name normalization, never fuzzy. Says WHO the party is, not that a loan is in special servicing. Unknown deal or role: OUT_OF_COVERAGE.

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_counterparty"
  }
}

Input Schema

NameRequiredDescriptionDefault
dealYesDeal name or alias, e.g. 'WFCM 2020-C58'.
roleNoDefault special_servicer. Full definitions ride each receipt's field_definition.
claimed_nameNoName to adjudicate (normalized comparison).

Output Schema

NameRequiredDescriptionDefault
as_ofYes
claimYesAdjudication: claimed_value, tolerance_*, within_tolerance, rationale.
messageYes
receiptYessf-receipt 0.3; schema https://cmdrvl.com/schemas/sf-receipt/v0/schema.json; context https://cmdrvl.com/contexts/obs-receipt/v0/context.json
claim_verdictYesCaller-claim verdict; DENY only here.
resolved_dealYesDeal resolution: matched, id, cik, candidates.

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. Changed23 schema fields changed
    • 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"
      -]
  3. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover read-only, idempotent, non-destructive and closed-world, so the description's job is to add semantics - and it does: single-source roster authority, non-fuzzy normalized comparison, the CONFIRM/DENY outcome shape, and an explicit OUT_OF_COVERAGE boundary. The 'master is the roster party, NOT the tape's primary servicer' note heads off a common wrong inference.

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?

The core adjudication framing is front-loaded and almost every sentence carries a distinct constraint (single-source, non-fuzzy, WHO-not-status, out-of-coverage). The telegraphic, dash-heavy phrasing and capitalized emphasis are efficient but slightly harder to parse than plain prose.

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?

With only three parameters, full schema coverage, an output schema and rich annotations, the description supplies exactly the missing pieces: comparison semantics, the coverage boundary, and the tape-vs-roster disambiguation. Nothing needed to call it correctly or interpret its verdict appears to be absent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline sits at 3; the description adds real meaning on top by specifying that claimed_name is compared under the ledger's name normalization and never fuzzily, and by framing role as roster-party identity. The deal parameter itself gets no extra description beyond the schema example.

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 uses a specific verb ('Adjudicate') against a named resource ('SEC 10-D counterparty roster') and scopes it to a single question ('who is the <role> on deal X'). It explicitly distinguishes itself from the ABS-EE tape's primary servicer and clarifies that it answers WHO, not servicing status, so an agent can separate it from the verify_deal_field / verify_loan_field siblings.

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?

Guidance is concrete: pass claimed_name to get CONFIRM/DENY under ledger normalization, treat unknown deal or role as OUT_OF_COVERAGE, and do not use it for special-servicing status questions. It never names a specific sibling tool to use instead, which is the only thing keeping this from a 5.

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.