Skip to main content
Glama

adverse_media

Read-only

Screen a company for 10 years of negative news, complaints, and bad reviews from news and review sites to identify reputational risks without register, sanctions, or PEP checks.

Instructions

Screen a company for negative news, complaints and bad reviews only (10-year news lookback, complaint and review sites).

    No register, sanctions or PEP screening: kyb_findings covers those
    and adverse media at the same price, so prefer it unless the user
    wants news and reviews only.
    Price: EUR 0.50 per call (a new account's first call is free).

    Args:
        company_name: Company to screen
        website: Company website URL for accuracy
    

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

Input Schema

NameRequiredDescriptionDefault
websiteNo
company_nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known; the description adds genuinely new behavioral facts on top: the 10-year lookback window, the data sources (complaint and review sites), the deliberate exclusion of register/sanctions/PEP coverage, and the cost of EUR 0.50 per call with a free first call. It stops short of stating turnaround time or what qualifies as 'negative', which keeps it off a 5.

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 purpose and scope are front-loaded in the opening sentence, and the pricing and routing guidance follow in short, self-contained lines. The trailing Args block largely duplicates the input schema and the stray indentation is noise, but no sentence is wasted.

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 a two-parameter screening call with annotations present and an output schema available, the description covers purpose, scope boundaries, sibling routing and cost. Nothing an agent needs in order to decide whether to call it, or to call it 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 description coverage is 0%, so the description carries the full burden, and its Args block only restates the two field names with thin glosses ('Company to screen', 'Company website URL for accuracy'). The note that website is used 'for accuracy' is the one piece of real added meaning; there is no format guidance or explanation of what happens when website is omitted (it defaults to empty).

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 and resource ('Screen a company for negative news, complaints and bad reviews') and bounds the scope in the same sentence with '10-year news lookback, complaint and review sites'. It also explicitly names what it is not ('No register, sanctions or PEP screening') so an agent can distinguish it from kyb_findings without inspecting either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit routing rule: prefer kyb_findings unless the user wants news and reviews only, because that tool covers the same ground at the same price. The when-not condition and the named alternative are both present, leaving nothing to inference.

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