Skip to main content
Glama
QuantLedger 73-Engine CPA, FASB GAAP, IRC Tax, Valuation & SEC 10-K MCP Server

QuantLedger 73-Engine CPA, FASB GAAP, IRC Tax, Valuation & SEC 10-K MCP Server

Official

Batch Screen US KYB, OFAC Sanctions, BIS, OIG Exclusions & SEC EDGAR (Cloud REST)

screen_us_kyb_ofac_bis_and_exclusions
Read-onlyIdempotent

Screens up to 5,000 entities against U.S. OFAC, BIS, ITAR, HHS OIG, and SEC watchlists to flag sanctions, denied-party, exclusion, and beneficial-ownership risks for KYB compliance.

Instructions

Screens 1 to 5,000 companies or individuals against 138,000+ live U.S. federal watchlist records (Treasury OFAC SDN/SSI/CMIC, Commerce BIS Entity List/Denied Persons, State Dept ITAR, HHS OIG Exclusions, OFAC 50%-Rule beneficial ownership, and SEC EDGAR CIK) via QuantLedger REST API (requires RAPIDAPI_KEY).

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": {
      "entities": "<entities>"
    },
    "name": "screen_us_kyb_ofac_bis_and_exclusions"
  }
}

Input Schema

NameRequiredDescriptionDefault
entitiesYesCompany/person names or objects with optional beneficial_owners ([{name, ownership_pct}]).
fuzzy_thresholdNoJaro-Winkler phonetic threshold (default 0.88).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv2.8.2

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered and the bar is lower. The description adds real value by disclosing the authentication requirement (RAPIDAPI_KEY) and the watchlist coverage breadth, but says nothing about result semantics, per-entity matching outcomes, rate limits, or cost. No contradiction with annotations — screening is correctly a read-only operation.

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?

A single front-loaded sentence with the verb, scale, coverage and dependency stated before the reader loses interest; there is essentially no filler. The nested parenthetical source list makes it dense and harder to scan, which keeps it just under the top mark.

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?

Given a two-parameter, fully documented schema and annotations covering safety and idempotency, the definition is sufficient to invoke correctly: scope, sources, batch limits and the API-key prerequisite are all stated. Residual gaps are return shape and per-call cost/limits, which are less critical for an idempotent read-only screening call with no output schema.

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%, with both parameters documented including the anyOf string-or-object entity shape and the 0.75–0.99 fuzzy threshold semantics, so the schema carries the burden and baseline is 3. The description only indirectly enriches this by naming "OFAC 50%-Rule beneficial ownership," which hints at the beneficial_owners field, but it adds no format or threshold guidance beyond the 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?

States a concrete verb and resource: "Screens 1 to 5,000 companies or individuals against 138,000+ live U.S. federal watchlist records," then enumerates the exact source lists (OFAC SDN/SSI/CMIC, BIS, ITAR, OIG Exclusions, SEC EDGAR). A batch screened-entity tool is unmistakably distinct from the sibling analytics/rates tools, so no explicit differentiation is needed.

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 batch bounds (1 to 5,000 entities, minItems 1) and by naming the required RAPIDAPI_KEY prerequisite, which is genuinely useful operator context. However, there is no statement of when to prefer this over a single-entity screening path, nor any exclusion or 'do not use for X' guidance.

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