entyrix-mcp

Screen a list of companies

screen_companies

Read-onlyIdempotent

Screen up to 25 companies per KYB request for supplier lists or portfolios; get compact rows (status, insolvency, sanctions, debts, verdict, coverage). INSUFFICIENT_DATA means not covered, not clean.

Instructions

Run kyb_check on up to 25 companies at once and get one compact row per company (status, insolvency, sanctions, debts, verdict, coverage). INSUFFICIENT_DATA = no findings but not covered by the core registers for that country — never report it as clean. Use for supplier lists or portfolios. Each company counts as one API request against your rate limit. Requires an authenticated account.

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": {
      "companies": "<companies>"
    },
    "name": "screen_companies"
  }
}

Input Schema

Name	Required	Description	Default
`companies`	Yes	Companies to screen.

Output Schema

Name	Required	Description	Default
`failed`	Yes
`results`	Yes
`screened`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Addedv0.2.2Nov 5, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds context annotations cannot express: one API request per company counts against the rate limit, an authenticated account is required, and INSUFFICIENT_DATA must never be read as clean. That last caveat is exactly the kind of misuse-preventing behavioral detail this dimension rewards.

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?

Four dense sentences: batching scope and output shape first, then the critical interpretation caveat, then use cases, then the operational constraints. Nothing is redundant with structured fields and nothing is padding.

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?

Output schema exists, yet the description still surfaces the row shape for at-a-glance planning; auth, rate-limit cost, batch ceiling, and the INSUFFICIENT_DATA pitfall are all covered. Nothing an agent needs to call this correctly is missing.

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 coverage is 100% and the nested ico/country semantics (including the country tie-break warning) are fully documented in the schema. The description only restates the 25-item cap already present as maxItems, adding no new parameter meaning. Baseline 3 applies.

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?

States a specific verb (run kyb_check) against a bounded resource (up to 25 companies) and enumerates the returned row fields (status, insolvency, sanctions, debts, verdict, coverage). It also implicitly distinguishes itself from the single-company kyb_check sibling, so an agent can choose without opening the schema.

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?

'Use for supplier lists or portfolios' gives a concrete triggering scenario, and the single-vs-batch relationship to kyb_check is implied by 'Run kyb_check on up to 25 companies at once.' No explicit 'use X instead when...' exclusion is stated, so it stops short of a 5.

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

Deploy Server