Skip to main content
Glama

analyze_scam_message

Check a suspicious SMS, WhatsApp, email, or call script for scam red flags.

Combines regional rule packs with an optional local HuggingFace AI scam model.

Args:
    message: The exact text of the suspicious message or call script.
    channel: Where it arrived (e.g. 'SMS', 'WhatsApp', 'Email', 'Phone Call').
    region: Regional scam pack to apply ('all', 'global', 'india', or 'us_uk').

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

Input Schema

NameRequiredDescriptionDefault
regionNoall
channelNoSMS/WhatsApp
messageYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description does real work by disclosing the two analysis engines: regional rule packs plus an optional local HuggingFace AI model, which tells the agent results are rule-driven and may be augmented by a local model. It does not state rate limits, latency, or that the call is non-mutating, which are minor gaps given the read-only 'check' framing.

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?

Purpose is front-loaded in one sentence, followed by a compact Args block with no filler. The Args block restates schema parameter names, but each line adds substantive detail (allowed region values, channel examples), so the redundancy earns its place.

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?

An output schema exists, so return values need not be explained, and the three-parameter surface is fully documented in the description. What remains unstated is behavior when the optional AI model is unavailable or how regions combine with 'all', which would help for a hybrid rule-plus-model tool.

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

Parameters5/5

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

Schema description coverage is 0% and no enums exist, so the description must compensate, and it does: it explains each of the three params, gives channel examples, and enumerates the valid region values ('all', 'global', 'india', 'us_uk') that the schema only hints at via a default. This is meaningfully more than the schema offers.

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 ('Check') against a specific resource ('suspicious SMS, WhatsApp, email, or call script') with a stated goal ('scam red flags'). This is clearly distinguishable from siblings like check_url_safety or check_email_breach, which target different artifacts.

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, but there is no explicit guidance on when to prefer this over check_url_safety or check_email_breach, and no exclusions or prerequisites. Usage is inferable but not spelled out.

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.