pathguard

check_transaction and preflight_transaction both analyze a crypto transaction for risk; the only real differentiator is the output shape (raw signals vs. an ALLOW/REVIEW/BLOCK decision). Batch, usage, and report tools are clearly distinct, but this one overlapping pair creates genuine misselection risk.

All five tools follow a clean snake_case verb_noun pattern (check_transaction, get_usage_status, preflight_transaction, report_scam_address). The plural variant check_transactions_batch is a natural, readable extension of the same convention.

Five tools is well-scoped for a focused transaction-risk-checking service. Each tool earns its place: single check, batch check, decision, usage, and reporting.

The surface covers the core lifecycle (check single, check batch, preflight decision, report scam, usage/quota). Minor gaps exist, such as no standalone address-risk check or retrieval of past scan results, but agents can work around these via the existing checks.