Skip to main content
Glama

Clearsignal Labs Token Scam Screen

Recent rug / collapse alerts

get_alerts
Read-onlyIdempotent

Most recent automated alerts: passing tokens that flipped to fail, or whose price collapsed, newest first. Heuristic, not proof of wrongdoing. NFA/DYOR.

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

Input Schema

NameRequiredDescriptionDefault
limitNoHow many alerts to return (1-50)

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?

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so safety and repeatability are covered. The description adds genuinely useful framing — results are heuristic and not proof of wrongdoing — plus newest-first ordering. It still omits the lookback window, what thresholds constitute 'failed' or 'collapsed', and whether results are paginated.

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 short sentences with the core purpose and ordering front-loaded, followed by the risk caveat. Nothing is padded or redundant.

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 one-optional-parameter read tool with no output schema, the description conveys enough to call it correctly: what an alert means, ordering, and how much to trust it. What remains thin is the shape of returned alerts and the time horizon covered.

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 100%: the single limit parameter already documents its 1-50 range, default of 10, and purpose. The description adds nothing about the parameter, so the baseline of 3 applies.

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 resource (automated alerts about tokens that flipped to fail or whose price collapsed) and states the ordering (newest first), which distinguishes it in substance from list_passing_tokens. It never names a sibling or explicitly routes the agent, so it falls 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 only implied: 'most recent ... newest first' suggests it is the tool for checking recent adverse events, and the caveat hints at how to treat results. There is no explicit when-to-use, when-not-to-use, or pointer to check_token / list_passing_tokens as alternatives.

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