Skip to main content
Glama

ScamNav

Get a scam case

get_scam_case

Retrieve one scam case by slug, including sections and FAQs, in the requested language. Use search_scams first to find a slug.

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": {
      "slug": "<slug>"
    },
    "name": "get_scam_case"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
slugYesCase slug, e.g. ftc-impersonation

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the tool retrieves a single case and includes sections and FAQs, but it does not mention error behavior for missing slugs, default language behavior, or the exact response shape.

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 with no wasted words, and the core retrieval behavior is front-loaded before the prerequisite. The structure is efficient and easy for an agent to scan.

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 two-parameter retrieval tool with no output schema and no annotations, the description covers the core purpose, the slug prerequisite, and the content returned. It is nearly complete, though it could mention default language behavior or slug-not-found handling.

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 slug field is documented in the schema itself, while the lang enum has no per-value explanation. The description adds that language is 'requested,' but it does not say what happens when lang is omitted or which language is default.

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 states a specific verb and resource — 'Retrieve one scam case by slug' — and clarifies that it returns sections and FAQs in the requested language. This distinguishes it from the sibling search tool, which finds slugs rather than retrieving a single case.

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?

It explicitly directs the agent to use search_scams first to find a slug, which is the key prerequisite for this tool. This is a clear when-to-use rule with a named alternative.

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