Skip to main content
Glama

Stratalize Intelligence

Get Aml Regulatory Benchmark

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/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety and data-source profile is covered. The description adds a genuinely useful non-schema detail: metered pricing at $0.50 USDC per call. It does not say whether the benchmarks are refreshed, cached, or how large a response is.

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?

Two sentences, front-loaded with the substantive content list, followed by audience and price. The enumeration is long but each item earns its place by defining scope. No filler or repetition of the title.

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 no output schema, the description partially compensates by listing what data categories the benchmarks cover. However, for a zero-required-parameter, 0%-schema-coverage tool, an agent still cannot predict response shape, default scope, or how the two enums change the result.

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%, so the description carries the full burden for the two enum parameters, yet it never mentions 'focus' or 'institution_type' or explains how enum values map to the listed content areas. It also leaves the no-required-parameter case ambiguous — it is unclear what an empty call returns. The topic list only loosely hints at the 'focus' enum values.

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 and enumerates its contents: FinCEN SAR filing rates, OFAC SDN counts, BSA enforcement fine history, travel rule thresholds, and staffing benchmarks. This is far more specific than the name alone and distinguishes it topically from siblings like get_bank_regulatory_benchmark. It stops short of an explicit verb, relying on the noun-phrase listing.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

The only guidance is an audience statement ('For compliance agents and financial institution risk officers'), which says who cares, not when to call this versus get_bank_regulatory_benchmark or get_regulatory_news_synthesis. There are no exclusions, prerequisites, or alternative-routing hints.

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