Skip to main content
Glama

ScamNav

Check scam risk

check_scam_risk

Analyze a suspicious message, email or text for known scam red flags using deterministic rules. Returns a risk level (LOW/MEDIUM/HIGH/CRITICAL) and the matched warning signs.

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

Input Schema

NameRequiredDescriptionDefault
langNo
textYesThe message or text to evaluate

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden. It usefully discloses the method (deterministic rules), the output scale (LOW/MEDIUM/HIGH/CRITICAL) and that matched warning signs come back, but it never states that the tool is side-effect-free/advisory-only, that results are heuristic and not a verdict, or how the 4000-character input cap is handled.

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?

Two sentences, no filler: the first states the action and method, the second states the return. Front-loaded and appropriately sized for a two-parameter tool.

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 simple read-only analyzer with no output schema, describing the return shape inline is the right call and largely closes the gap. The one missing piece is the `lang` parameter's meaning and default behavior, which matters given the 16-value enum.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: `text` is documented, but `lang` (a 16-value enum) is not described anywhere. The description never mentions language handling — whether lang is auto-detected, whether omitting it degrades accuracy, or which languages the rule set covers — so it fails to compensate for the schema gap.

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?

"Analyze a suspicious message, email or text for known scam red flags" gives a specific verb (analyze) and resource (message text), and the deterministic-rules framing plus risk-level output sets it apart from the lookup-style siblings (get_scam_case, search_scams). It stops short of naming a sibling as the alternative path, so it is clear but not maximally differentiated.

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 word "suspicious" implies the trigger condition (user pastes something that looks like a scam), but there is no explicit when-to-use, when-not-to-use, or routing to list_scam_types / search_scams. An agent must infer the boundary from the sibling names alone.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources