Skip to main content
Glama

AI Fusion One

Basic verification

basic_verification

Evidence report for a supplier (name and/or website) or a product (GTIN/UPC or name) from free public sources (Wikidata, DNS, HTTPS/TLS, RDAP, GLEIF incl. parents, GTIN check digit, Open Food/Products/Beauty Facts). For suppliers it also screens the name against OFAC/UK/UN sanctions lists (possible match - manual review; never a clearance), validates an EU VAT number via VIES (vat_number) and queries keyless registries for FR, NO, CZ, FI and PL (country, registry_id; PL needs the KRS number). Each check is verified, unverified or contradictory with source and timestamp. Not an authenticity or fraud guarantee. PAID tool: call without x402_payment to get the payment requirements. Price: $0.10 per call. TESTNET ONLY: priced in Base Sepolia test USDC (no real value).

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": {
      "subject_type": "<subject_type>",
      "subject": "<subject>"
    },
    "name": "basic_verification"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNo
brandNo
trialNoFree trial instead of payment: a few calls per client per UTC day (shared across paid tools); result marked mode=trial.
countryNoSupplier country, ISO alpha-2 (e.g. DE, FR, NO, CZ, FI, PL).
subjectYesSupplier name, product name, or GTIN/UPC.
websiteNoClaimed public website/domain (no port or credentials).
vat_numberNoEU VAT number incl. prefix, e.g. DE811128135.
registry_idNoNational registry id (needs country): SIREN/SIRET FR, org no. NO, IČO CZ.
subject_typeYesWhat is being verified.
x402_paymentNoBase64 x402 v1 'exact' EIP-3009 payment payload for Base Sepolia (TESTNET test USDC, no real value). Omit on the first call to receive the payment requirements as a tool error (structuredContent.accepts); sign them and call again with this argument. One payment funds exactly one call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Goes well beyond the annotations (readOnly=false, openWorld=true, idempotent=false, destructive=false) by disclosing cost ($0.10/call), the testnet-only nature of the payment, the exact x402 payment handshake (omit x402_payment on first call, receive structuredContent.accepts, retry), the trial-mode fallback, and the result taxonomy (verified/unverified/contradictory with source and timestamp). It also qualifies the sanctions match as possible-match/manual-review rather than clearance. None of this contradicts 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.

Conciseness4/5

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

Information is front-loaded: what the report covers, then sanctions/VAT/registry specifics, then result semantics, then payment mechanics. It is a single dense paragraph with some parenthetical stacking, but nearly every clause carries operational value. Splitting the payment instructions into their own sentence would improve scanability.

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

Completeness4/5

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

For a 10-parameter, no-output-schema tool this is strong coverage: it explains subject_type branching, the payment protocol, and what the results contain. Minor gaps remain around how optional parameters combine (e.g. brand vs name for products, whether country alone suffices for registry lookups) and no indication of rate limits beyond trial quotas.

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

Parameters4/5

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

With 80% schema coverage the baseline is 3, and the description adds real meaning: vat_number is validated via VIES, country plus registry_id drive the FR/NO/CZ/FI/PL registries, PL specifically requires a KRS number, and GTIN check-digit validation applies to product subjects. Only the brand and subject_type parameters get no extra elaboration beyond the schema.

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 concrete deliverable (an evidence report) and enumerates the exact inputs it accepts (supplier name/website, product GTIN/UPC or name) plus the data sources it queries (Wikidata, DNS, HTTPS/TLS, RDAP, GLEIF, GTIN check digit, Open Food/Products/Beauty Facts). An agent can tell this is a multi-source verification aggregator rather than a simple lookup. It stops short of naming a sibling (e.g. basic_lookup or web_check) to contrast against, so it does not reach the top band.

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

Usage Guidelines4/5

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

Clear context for when to call: supplier or product subject, with the sub-branches spelled out (sanctions screening for suppliers, VIES for vat_number, national registries needing country, PL needing the KRS number). It also sets expectations about when-not to rely on it ('never a clearance', 'not an authenticity or fraud guarantee'). No explicit alternative-tool routing is given, which keeps it at 4.

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