predictionguard

pg_kyc_bundle_entity

Full KYC bundle for a named entity: sanctions + PEP + adverse media + country risk in a single call. Delegates to AMLOracle.kyc_bundle.

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

Input Schema

Name	Required	Description
`name`	Yes
`country`	No	ISO country code
`entity_type`	No	'person' or 'organization'

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 7, 2026

TDQS

B3.3/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only describes what the tool does and mentions delegation to AMLOracle, but it does not state whether it is a read-only operation, the nature of side effects, rate limits, or failure behavior. This is insufficient for a tool with no annotation backup.

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?

The description is concise, with two sentences that front-load the purpose. The second sentence about delegation is of limited value to an agent but does not add significant clutter. Overall, it is efficiently written.

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

Completeness2/5

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

This is a complex composite tool with no output schema, yet the description does not explain what the response contains, how results are aggregated, or any operational caveats. Given the lack of annotations and output schema, more context is needed for safe and correct invocation.

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 description coverage is 67%, with country and entity_type having descriptions. The description adds that the tool is for a 'named entity' and includes 'country risk', which hints at the name and country parameters. However, it does not clarify the expected format or constraints for the name parameter beyond being an entity identifier.

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?

The description clearly states the tool performs a full KYC bundle (sanctions, PEP, adverse media, country risk) for a named entity in a single call. This distinguishes it from sibling tools that offer individual checks, such as pg_sanctions_screen_entity and pg_pep_check_entity.

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?

The phrase 'Full KYC bundle' and 'in a single call' implies use when comprehensive screening is desired, but it does not explicitly mention when to use individual sibling tools instead. There are no named alternatives or exclusions, so guidance is only implied.

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

All predictionguard 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?