Skip to main content
Glama

get_red_flags

Read-only

Red flags that a crypto trading bot or 'AI trading' offer may be a scam, plus regulator lookup links.

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_red_flags"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

The readOnlyHint annotation already tells the agent this is a safe read with no side effects. The description adds that the payload includes regulator lookup links, which is useful return context in the absence of an output schema. It does not say whether the flags are static curated content or live-fetched, nor how many or in what structure they arrive.

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?

A single sentence with no filler, with the primary content (red flags) front-loaded ahead of the secondary content (regulator links). The fragmentary noun-phrase construction is compact but slightly less scannable than a verb-led statement.

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 zero-parameter, read-only reference lookup with no output schema, the description covers what the tool returns and enough about the domain to call it correctly. Only a rough sense of output shape or size is missing, which is minor at this complexity level.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies it is a parameterless lookup that returns the same reference material every call.

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 names a specific content set: red flags indicating a crypto trading bot or 'AI trading' offer may be a scam, plus regulator lookup links. That is clearly distinguishable from siblings like get_safe_key_checklist or get_required_permissions. It avoids a 5 because it is a noun phrase with no verb and never explicitly contrasts itself with the other get_* lookups.

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 only implied by the subject matter: an agent can infer it should call this when assessing whether a crypto trading offer is fraudulent. There is no explicit 'use when' condition, no exclusion, and no mention of when a sibling such as get_safe_key_checklist would be the better call.

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