Stratum UK compliance checks

Run a whole letting, sale, client or export shipment check (charged)

run_suite_check

Runs a whole job in one call and issues one signed certificate: a letting (tenant, landlord, guarantor), a sale (buyer, seller), a finance client (client, director, counterparty) or an export shipment (buyer, consignee, endUser, intermediateConsignee, forwarder, supplier, with a destination). Everyone named is screened for sanctions, each company with a number gets its owners screened, and a property postcode adds the property risk pack; an export shipment screens each party against the US export lists too and reads the UK and US measures on the destination (a screening record, not a licensing decision). PAID from your Stratum API balance (free on a test key): confirm with the user first. PEP and adverse media are not run from here.

Input Schema

Name	Required	Description
`goods`	No	Export: the goods as the firm describes them (never classified).
`suite`	Yes
`parties`	Yes	The people and companies on the job.
`postcode`	No	Letting or sale: the property postcode (adds the property risk pack).
`matterRef`	No	Your own reference for the job, printed on the certificate.
`issuerName`	No	The firm the certificate names as issuer, if not your account firm.
`destination`	No	Export: the two-letter ISO code of the destination country.
`addressLine1`	No	Letting or sale: the first line of the property address.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 20, 2026

addedInput schema / properties / destination

Added value: +{
+  "description": "Export: the two-letter ISO code of the destination country.",
+  "type": "string"
+}

addedInput schema / properties / goods

Added value: +{
+  "description": "Export: the goods as the firm describes them (never classified).",
+  "type": "string"
+}

addedInput schema / properties / parties / items / properties / country

Added value: +{
+  "description": "Export: the two-letter ISO code of the country the party is in.",
+  "type": "string"
+}

changedInput schema / properties / parties / items / properties / role / description

Previous value: -"letting: tenant, landlord, guarantor. sale: buyer, seller, payer. finance: client, director, counterparty."New value: +"letting: tenant, landlord, guarantor. sale: buyer, seller, payer. finance: client, director, counterparty. export: buyer, consignee, endUser, intermediateConsignee, forwarder, supplier."

changedInput schema / properties / suite / enum

Previous value: -[
-  "letting",
-  "sale",
-  "finance"
-]New value: +[
+  "letting",
+  "sale",
+  "finance",
+  "export"
+]

First observedOct 12, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Adds substantial context beyond the annotations: paid from the Stratum API balance (free on a test key), requires user confirmation, produces a signed certificate, adds a property risk pack when a postcode is given, screens owners of numbered companies, and frames output as "a screening record, not a licensing decision." That cost, confirmation and scope-disclaimer information is exactly what annotations cannot convey.

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?

Front-loads the core action and cost/confirmation warning early, and every clause carries information. It is a dense run-on paragraph rather than scannable structure, which costs it a point, but there is little redundancy.

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?

For an 8-parameter, non-idempotent, paid, open-world tool with no output schema, the description covers what is checked, what is deliberately excluded, what the deliverable is (one signed certificate), and who pays. Nothing an agent needs before invoking or confirming with the user is missing.

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?

Schema coverage is 88%, so the baseline is 3, but the description goes further by tying parameters to conditional behavior: which roles each suite expects, that a companyNumber triggers owner screening, that a postcode adds the property risk pack, and that destination drives UK/US measures. That is meaning beyond the schema's field-level text.

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?

Opens with a specific verb and outcome ("Runs a whole job in one call and issues one signed certificate") and then enumerates the four suites and their party roles. An agent can immediately distinguish this bundled job tool from single-purpose siblings like screen_sanctions, postcode_report or fca_firm.

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 use — one call covering an entire letting/sale/finance/export job — plus explicit exclusions ("PEP and adverse media are not run from here") and the precondition "confirm with the user first" before spending. It never explicitly names the sibling to use for a single-party check, so it stops short of full alternative routing.

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

All Stratum UK compliance checks tools Inspect

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

Need Help?