Skip to main content
Glama

BRAINIAC OFAC & UK Sanctions Screening

Normalize a vendor identity

exclusion_normalize

Normalize identifiers before source screening. This operation does not determine eligibility. Price $0.01 USDC. POST /api/v1/exclusion/normalize. Unpaid calls return 402 and do not run.

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": {
      "legalName": "<legalName>"
    },
    "name": "exclusion_normalize"
  }
}

Input Schema

NameRequiredDescriptionDefault
legalNameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does so well on operational traits: cost ($0.01 USDC), HTTP method/path, and explicit failure behavior (unpaid calls return 402 and do not run). It also disclaims that this is not an eligibility determination. Missing only idempotency/caching behavior and whether repeat calls are re-billed.

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?

Four short sentences, purpose front-loaded, then constraints, then price and endpoint. No filler; pricing and endpoint are arguably operational metadata but they are genuinely useful for an agent deciding whether to call.

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?

For a one-parameter paid POST with no output schema, the biggest remaining gap is the return shape: the agent cannot tell whether it gets back a normalized string, a diff, or a structured identity object. Workflow position, cost, and error behavior are covered, so it is adequate but not complete.

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 must explain the single parameter, and it does not mention legalName, its 1-240 character bounds, or what normalization does to the input (case folding, punctuation stripping, transliteration). Only the generic word 'identifiers' hints at the input, leaving the sole parameter essentially undocumented.

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?

States a specific verb and resource ('Normalize identifiers') and positions it in the workflow ('before source screening'), which separates it from the screening siblings. Slightly ambiguous whether 'identifiers' means only the legalName field, since the title says 'vendor identity' while the schema says 'legalName'.

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?

There is sequencing guidance ('before source screening') and a negative constraint ('does not determine eligibility'), which steers the agent away from treating output as a screening verdict. However, no sibling is named as the follow-up step (e.g. exclusion_screen) and there is no guidance on when normalization can be skipped.

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