Skip to main content
Glama
CyberSafe MCP

CyberSafe MCP

by kshitij9896

analyze_scam_message

Checks suspicious SMS, WhatsApp, email, or call scripts for scam red flags using regional rules and an optional local AI model.

Instructions

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 observedv0.3.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It helpfully discloses the detection method (regional rule packs plus an optional local HuggingFace model, implying local processing), but omits whether submitted text is stored or logged, any length limits, and whether the AI model must be installed. Return-value detail is not required since an output schema exists.

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 sentence is front-loaded and wastes no words, and the Args block is compact and scannable. The Python-docstring formatting is slightly awkward for a JSON-consumed definition but adds real information for all three parameters.

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?

All three parameters are explained, the allowed region set is surfaced, and the detection approach is disclosed; an output schema exists so return values need no prose. The remaining gaps (data retention, message size limits, dependency on a local model) are modest rather than blocking for a read-only analysis tool.

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

Parameters4/5

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

Schema description coverage is 0%, so the description must compensate, and it largely does: it defines 'message' as the exact text, gives example values for 'channel', and enumerates the legal 'region' values ('all', 'global', 'india', 'us_uk'), which the schema does not. The only weakness is a mismatch with the schema's default channel value 'SMS/WhatsApp' versus the examples 'SMS'/'WhatsApp'.

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?

States a specific verb ('check') and resource ('suspicious message or call script') and enumerates the input channels (SMS, WhatsApp, email, call script). That resource is unmistakably distinct from the URL, password, and email-breach siblings, though the description never names an alternative to route against.

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?

Usage is implied by 'check a suspicious ... message', which tells an agent the input is untrusted content, but there is no explicit when-to-use/when-not or pointer to a sibling such as check_url_safety for a suspicious link inside the message. Nothing states prerequisites or what to do when a message contains both a link and text.

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