Skip to main content
Glama

HelpMyAgent

by io.github.helpmyagent
OverviewDiscussionsAdmin

Public Sanctions Name Screen

compliance_name_screen

Screens a name against integrated French, UK and UN public sanctions/freezing lists using explainable fuzzy matching. Use when: Screen a person or organization name against public sanctions lists. You have a person or organization name and need explainable screening against the supported French, UK and UN public sanctions lists. You need candidate matches with fuzzy-match scores before manual review. Avoid when: You have a French company identifier and want company-aware public compliance checks; use company/fr/compliance. You need a complete commercial AML/KYC database or a legal guarantee that a subject is unsanctioned. Limitations: Fuzzy name matching can produce false positives and false negatives, especially for aliases, transliteration and common names. No match means only that no candidate was found in the supported public lists at check time. Price: 0.020 USD per call via x402. Paid-call behavior: source records are not modified, but a successful invocation can consume the advertised x402 payment; the payment-required challenge is free, and repeating the tool after a completed paid invocation may require a new payment. Accepted x402 networks: eip155:8453, xrpl:0.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPerson or organization name to compare with the supported public sanctions and asset-freeze lists. (minimum length 2; maximum length 200).
thresholdNoMinimum fuzzy-match score accepted as a candidate public-list match. (minimum 50; maximum 100; default 85).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesPublicly available company, person, buyer or record name for this result.
statusYesNormalized endpoint or source status.
matchesYesCandidate public-list or source matches returned by the endpoint.
sourcesYesPublic data sources used or checked for this result.
thresholdYesStructured value returned for “threshold” as defined by this API contract.
checked_atYesUTC timestamp at which HelpMyAgent performed the check.
limitationsNoKnown interpretation, source-coverage or freshness limitations for this result.
match_countYesNumber of candidate matches returned by the screening operation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / required
      Previous value: -[
-  "name",
-  "threshold",
-  "status",
-  "match_count",
-  "matches",
-  "sources",
-  "checked_at",
-  "limitations"
-]New value: +[
+  "name",
+  "threshold",
+  "status",
+  "match_count",
+  "matches",
+  "sources",
+  "checked_at"
+]
  2. Changed21 schema fields changed
    • addedInput schema / description
      Added value: +"Structured input parameters for the compliance/name-screen API."
    • addedInput schema / properties / name / description
      Added value: +"Person or organization name to compare with the supported public sanctions and asset-freeze lists. (minimum length 2; maximum length 200)."
    • addedInput schema / properties / threshold / description
      Added value: +"Minimum fuzzy-match score accepted as a candidate public-list match. (minimum 50; maximum 100; default 85)."
    • addedOutput schema / description
      Added value: +"Structured result returned by the compliance/name-screen API."
    • addedOutput schema / properties / checked_at / description
      Added value: +"UTC timestamp at which HelpMyAgent performed the check."
    • addedOutput schema / properties / limitations / description
      Added value: +"Known interpretation, source-coverage or freshness limitations for this result."
    • addedOutput schema / properties / match_count / description
      Added value: +"Number of candidate matches returned by the screening operation."
    • addedOutput schema / properties / matches / description
      Added value: +"Candidate public-list or source matches returned by the endpoint."
    • addedOutput schema / properties / matches / items / properties / name / description
      Added value: +"Publicly available company, person, buyer or record name for this result."
    • addedOutput schema / properties / matches / items / properties / reference / description
      Added value: +"Structured value returned for “reference” as defined by this API contract."
    • addedOutput schema / properties / matches / items / properties / score / description
      Added value: +"Normalized score produced by the endpoint; interpretation is defined by the tool description and limitations."
    • addedOutput schema / properties / matches / items / properties / source / description
      Added value: +"Structured value returned for “source” as defined by this API contract."
    • addedOutput schema / properties / matches / items / properties / type / description
      Added value: +"Structured value returned for “type” as defined by this API contract."
    • addedOutput schema / properties / name / description
      Added value: +"Publicly available company, person, buyer or record name for this result."
    • addedOutput schema / properties / sources / description
      Added value: +"Public data sources used or checked for this result."
    • addedOutput schema / properties / sources / items / properties / publication_date / description
      Added value: +"Structured value returned for “publication date” as defined by this API contract."
    • addedOutput schema / properties / sources / items / properties / records_scanned / description
      Added value: +"Structured value returned for “records scanned” as defined by this API contract."
    • addedOutput schema / properties / sources / items / properties / source / description
      Added value: +"Structured value returned for “source” as defined by this API contract."
    • addedOutput schema / properties / sources / items / properties / status / description
      Added value: +"Normalized endpoint or source status."
    • addedOutput schema / properties / status / description
      Added value: +"Normalized endpoint or source status."
    • addedOutput schema / properties / threshold / description
      Added value: +"Structured value returned for “threshold” as defined by this API contract."
  3. Added

TDQS

A4.7/5.0
Behavior5/5

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

Despite readOnlyHint/idempotentHint false, the description discloses that source records are not modified but a successful paid invocation can consume x402 payment, that the payment-required challenge is free, and that repeat calls may require new payment. It also surfaces fuzzy-match false positives/negatives and the meaning of a no-match result, going well beyond the annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core action and then organized into clear labeled sections (Use when, Avoid when, Limitations, Price, Paid-call behavior, Accepted networks). Each section earns its place; there is no filler or redundant elaboration.

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 an output schema present, return-value documentation is not required, and the description covers the remaining decision-relevant context: when to use, when not to use, limitations, price, payment side effects, and accepted x402 networks. An agent has everything needed to invoke it correctly.

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%: both name and threshold are already described with constraints and defaults. The description adds context about fuzzy-match scores and candidate matches but does not add parameter-level detail beyond the schema, so baseline 3 is appropriate.

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 opening sentence names a specific verb and resource: screens a name against integrated French, UK and UN public sanctions/freezing lists with explainable fuzzy matching. The 'Avoid when' section explicitly distinguishes it from company/fr/compliance by pointing to company-identifier use, so it is clearly differentiated from siblings.

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

Usage Guidelines5/5

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

The description provides explicit 'Use when' and 'Avoid when' guidance, including the concrete alternative company/fr/compliance for French company identifiers and exclusions for full AML/KYC or legal guarantees. This tells an agent exactly when to select this tool versus alternatives.

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

All HelpMyAgent toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources