predictionguard

pg_adverse_media_entity

Adverse media scan — negative news on fraud, money laundering, corruption, sanctions. Delegates to AMLOracle. Core building block for evidence chains that link a wallet or trader to publicly reported concerns (always cite the source, never attribute).

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_adverse_media_entity"
  }
}

Input Schema

Name	Required	Description
`lang`	No	Optional language (e.g. en, de)
`name`	Yes	Person or entity name
`limit`	No	Max results (default upstream)

Schema Changelog

Changes observed during successful MCP inspections.

First observedMay 7, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the full burden. It reveals a key behavioral trait: delegation to AMLOracle, and implies results include sources to cite. However, it does not disclose whether the operation is read-only, potential data sensitivity, rate limits, or any side effects. This is a moderate level of transparency but not comprehensive.

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?

The description is three sentences, front-loaded with the primary purpose. Each sentence earns its place: what it scans, how it works (AMLOracle), and usage guidance. No redundancy or filler.

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?

The description covers purpose, delegation, and user guidance, which is solid for a tool with three simple parameters. However, it does not describe the output format or result presentation, and with no output schema, that would be helpful. Overall, it is mostly complete but not exhaustive.

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 100% (name, lang, limit all have descriptions). The tool description itself does not add semantics beyond the schema, simply framing the operation as a 'scan' by name. With full schema coverage, a baseline 3 is appropriate.

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 clearly identifies the tool as an adverse media scan for negative news on specific crime types (fraud, money laundering, corruption, sanctions), which distinguishes it from siblings focused on PEP checks or sanctions screening. However, it does not explicitly compare itself to those adjacent tools, so it misses the full sibling differentiation.

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?

The description states it is a 'core building block for evidence chains' linking a wallet or trader to publicly reported concerns, giving a clear when-to-use context. It also provides a usage rule ('always cite the source, never attribute'). It does not explicitly say when not to use it or name alternatives, but the context is sufficient for an agent to infer appropriate usage.

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?