Skip to main content
Glama

get_aml_regulatory_benchmark

Read-only

AML regulatory benchmarks — FinCEN SAR filing rates, OFAC SDN counts and recent additions, BSA enforcement fine history, travel rule thresholds, and compliance staffing benchmarks. For compliance agents and financial institution risk officers. $0.50 USDC per call.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_aml_regulatory_benchmark"
  }
}

Input Schema

NameRequiredDescriptionDefault
focusNo
institution_typeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already establish readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds information the annotations do not: a per-call price of $0.50 USDC, which matters for an agent deciding whether to invoke it. It stops short of disclosing data freshness, time coverage, or whether 'recent additions' is bounded.

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, front-loaded with the resource and its contents, followed by audience and then price; nothing is padded. The telegraphic noun-phrase style is efficient, though it trades away the explicitness that would have resolved the parameter gaps.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With only two optional enum parameters and no output schema, this is a low-complexity tool and the description covers its subject matter and cost. However, it omits what the response contains, the time window of the benchmarks, and how the optional filters change the result, which leaves an agent guessing about defaults and output shape.

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

Parameters2/5

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

Schema description coverage is 0% and both parameters are bare enums, so the description carries the full burden. The topic list loosely maps to the 'focus' values (enforcement, sar_filing, ofac), but 'institution_type' is never addressed, no defaults are stated for the optional parameters, and the mapping is left to inference rather than stated.

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?

The description names a specific resource (AML regulatory benchmarks) and enumerates its concrete contents: FinCEN SAR filing rates, OFAC SDN counts, BSA fine history, travel rule thresholds, staffing benchmarks. An agent can tell this is an AML-specific data retrieval tool. It does not explicitly contrast with the closely named sibling get_bank_regulatory_benchmark, 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 Guidelines3/5

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

The audience framing ('For compliance agents and financial institution risk officers') implies when the tool is relevant but never states when to prefer it over alternatives such as get_bank_regulatory_benchmark or get_regulatory_news_synthesis. No exclusions or preconditions are given, so usage must be inferred from the topic list.

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.

Resources