Axiom Works AgentReader

kyb_report

Use this for one-shot agent KYB: UK Companies House DD and/or Australia ASIC (acn) and/or Canada (ca_number/bn) and/or France (siren/siret) and/or Norway Brreg (orgnr) and/or Denmark CVR (cvr) and/or Finland PRH (ytunnus/businessId) and/or Switzerland Zefix (uid) and/or Poland KRS (krs/nip) and/or Czech ARES (ico) and/or Belgium CBE/KBO (enterprise_number/be) and/or Slovakia RPO (sk/ico_sk/rpo) and/or Ireland CRO (ie) and/or Estonia äriregister (ee) and/or Latvia (lv) and/or Singapore ACRA (sg/uen) and/or US state SOS registries NY/CO/CT/OR/TX/VA (us_state+us_id or us_name) + EU VIES VAT + optional GLEIF LEI (with ownership parents) + website research + sanctions screen (entity+directors) + director appointment skim → trust flag. Screening only, not a regulated determination. Example: {enterprise_number:"0202239951"} or {sk:"31322832"} or {sg:"196800306E"}. $2.50 USDC. Related: UK-only cheaper: /uk-dd $1; emails: /email-check $0.002; screen extra names: /sanctions $0.05 (OFAC/UK/UN/EU); batch <=50: /sanctions-batch $1; officer appointments: /uk-officer $0.15; GLEIF LEI: /lei $0.005.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kyb_report"
  }
}

Input Schema

Name	Required	Description	Default
`be`	No
`bn`	No
`ch`	No
`cz`	No
`ee`	No
`fi`	No
`id`	No
`ie`	No
`lv`	No
`pl`	No
`sg`	No
`sk`	No
`acn`	No
`bce`	No
`che`	No
`cvr`	No
`ico`	No
`kbo`	No
`krs`	No
`lei`	No
`nip`	No
`rpo`	No
`uen`	No
`uid`	No
`vat`	No
`name`	No
`orgnr`	No
`siren`	No
`siret`	No
`state`	No
`us_id`	No
`domain`	No
`ico_sk`	No
`number`	No
`country`	No
`us_name`	No
`ytunnus`	No
`us_state`	No
`ca_number`	No
`businessId`	No
`company_id`	No
`vat_number`	No
`jurisdiction`	No
`enterprise_number`	No
`registration_number`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedNov 7, 2026
- addedInput schema / properties / ee
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / ie
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / lv
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / sg
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / uen
```
Added value: +{
+  "type": "string"
+}
```
Changed5 schema fields changedNov 7, 2026
- addedInput schema / properties / company_id
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / id
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / jurisdiction
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / registration_number
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / state
```
Added value: +{
+  "type": "string"
+}
```
Changed3 schema fields changedNov 7, 2026
- addedInput schema / properties / us_id
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / us_name
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / us_state
```
Added value: +{
+  "type": "string"
+}
```
Changed3 schema fields changedNov 7, 2026
- addedInput schema / properties / ico_sk
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / rpo
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / sk
```
Added value: +{
+  "type": "string"
+}
```
Changed4 schema fields changedNov 7, 2026
- addedInput schema / properties / bce
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / be
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / enterprise_number
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / kbo
```
Added value: +{
+  "type": "string"
+}
```

Changed8 schema fields changedNov 7, 2026

addedInput schema / properties / ch
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / che
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / cz
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / ico
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / krs
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / nip
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / pl
```
Added value: +{
+  "type": "string"
+}
```
addedInput schema / properties / uid
```
Added value: +{
+  "type": "string"
+}
```

Changed3 schema fields changedNov 7, 2026
- addedInput schema / properties / businessId
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / fi
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / ytunnus
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedNov 7, 2026
- addedInput schema / properties / cvr
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedNov 6, 2026
- addedInput schema / properties / orgnr
```
Added value: +{
+  "type": "string"
+}
```
Changed2 schema fields changedNov 6, 2026
- addedInput schema / properties / siren
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / siret
```
Added value: +{
+  "type": "string"
+}
```
Changed1 schema field changedNov 6, 2026
- addedInput schema / properties / lei
```
Added value: +{
+  "type": "string"
+}
```
Changed3 schema fields changedNov 5, 2026
- addedInput schema / properties / acn
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / bn
```
Added value: +{
+  "type": "string"
+}
```
- addedInput schema / properties / ca_number
```
Added value: +{
+  "type": "string"
+}
```
AddedNov 5, 2026

TDQS

A3.9/5.0

Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose cost ($2.50 USDC), scope boundaries ('Screening only, not a regulated determination'), and included behaviors such as GLEIF ownership parents, director-level sanctions screening, and website research. It still omits auth requirements, rate limits, latency, and failure handling across the many upstream registries.

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

Conciseness3/5

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

The purpose and disclaimer are front-loaded, and most tokens carry real information, but the bulk is delivered as one long slash-separated run-on sentence that is hard to scan, with country mappings interleaved with pricing and sibling routing in a single block.

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 45-parameter aggregator with no annotations and no output schema, the definition covers purpose, cost, legal-status disclaimer, included data sources, examples, and sibling routing. The main gap is that, without an output schema, the description gives only a hint ('→ trust flag') about the report's actual return structure.

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 0% across 45 parameters, and the description compensates by mapping many keys to jurisdictions and identifiers (acn→ASIC, siren/siret→France, orgnr→Norway, cvr→Denmark, uid→Zefix, krs/nip→Poland, sg/uen→Singapore, us_state+us_id or us_name→US states) plus concrete JSON examples. However, a substantial remainder (name, domain, lei, vat, jurisdiction, company_id, number, country, registration_number, ch, cz, fi, id, bce, che, kbo) is left entirely unexplained.

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 specific deliverable — a one-shot KYB report aggregating Companies House DD, ASIC, EU registries, VIES, GLEIF LEI, website research, sanctions screening, and a trust flag — so the resource and outputs are identifiable. It partially differentiates from siblings by naming cheaper alternatives (uk-dd, sanctions, lei), though the country/param enumeration makes the core purpose less crisp than it could be.

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?

It opens with 'Use this for one-shot agent KYB' and then routes the agent away with cost-labeled alternatives: UK-only via /uk-dd at $1, extra-name screening via /sanctions at $0.05, batch via /sanctions-batch at $1, officer appointments via /uk-officer. The only gap is the absence of explicit when-not-to-use conditions beyond the cheaper-alternative hints.

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

All Axiom Works AgentReader 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.