Skip to main content
Glama

ScamNav

Get reporting resources

get_reporting_resources

List official scam/cybercrime reporting channels. Optionally filter by region code. Only official authorities are included; no recovery or fund-recovery services.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_reporting_resources"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
regionNoOptional region code, e.g. US, HK, IN

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries the burden but does disclose useful scoping behavior: only official authorities are returned, recovery services are excluded, and filtering is optional. It does not describe what a returned channel record looks like (URL, phone, hours) or the default behavior when region is omitted, leaving meaningful gaps for a no-annotation tool.

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?

Three short sentences, front-loaded with the core action, followed by the optional filter and the scope boundary. No redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-optional-parameter listing tool, most of what an agent needs is present, and no output schema exists so return-value detail isn't strictly required. However, the description omits any mention of the lang parameter and gives no hint about what data a channel entry contains, which would help an agent decide whether the result is usable.

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 50%: the region parameter is documented in the schema and reinforced in the description ('filter by region code'), but the lang parameter has no description anywhere—only an enum of language codes implies its purpose, and the description never mentions it. That leaves the more ambiguous parameter unexplained.

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?

The description opens with a specific verb and resource: 'List official scam/cybercrime reporting channels.' It immediately distinguishes itself from siblings like get_scam_case or check_scam_risk, which handle cases and risk rather than directory lookup, so an agent can tell them apart without opening a schema.

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?

It gives a clear usage context (finding official reporting channels) and an explicit scope exclusion: 'no recovery or fund-recovery services,' which steers the agent away from misusing this for fund recovery lookups. It does not name a sibling alternative for adjacent needs, which keeps it out of 5 territory.

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