Skip to main content
Glama

ScamNav

Search scam cases

search_scams

Search the ScamNav anti-scam knowledge base by keyword across titles, summaries, tags and scam types. Returns matching cases in the requested language.

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": {
      "query": "<query>"
    },
    "name": "search_scams"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNo
queryYesKeyword, brand, domain or tactic to search

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the behavioral burden. It discloses which fields are searched and that results come back in the requested language, but says nothing about result caps, ranking/ordering, pagination, or behavior on zero matches — meaningful gaps for a search endpoint.

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 tight sentences with the capability front-loaded and the return behavior second. Nothing is redundant or padded.

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 two-parameter read-only search with no output schema and no annotations, the description covers what is searched and the language dimension, which is most of what matters. It still leaves the agent guessing about result volume, ordering, and empty-result behavior.

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 coverage is 50%: the 'query' param is documented in the schema as keyword/brand/domain/tactic, while 'lang' has only an enum. The description partially compensates by clarifying that lang controls the language of the returned cases, but it does not add matching semantics (exact vs fuzzy, multi-word handling) for query.

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?

The description states a concrete verb and resource — 'Search the ScamNav anti-scam knowledge base' — and enumerates the indexed fields (titles, summaries, tags, scam types), so an agent can tell this is a keyword search rather than a single-record lookup. It does not name siblings such as get_scam_case or check_scam_risk explicitly, so it stops short of full differentiation.

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 'search by keyword' versus the record-fetching siblings, but the description never says when to prefer this over get_scam_case or check_scam_risk, and gives no exclusions or prerequisites. An agent must infer the routing decision from 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