Skip to main content
Glama

Bulk screener

bulk_screener

PAYWALLED. Returns top 200 X1 tokens with full metadata. Returns x402 payment instructions to call /api/x402/screener-bulk for $0.025.

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": "bulk_screener"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

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?

With no annotations, the description carries the full burden, and it does disclose the most critical behavior: calling this returns x402 payment instructions for /api/x402/screener-bulk, not the token data itself, at a stated $0.025. That is a real non-obvious trait. It stops short of describing what happens after payment, whether the returned payment quote expires, or how the paid data is delivered.

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?

Two tight sentences with no filler. Leading with 'PAYWALLED' is unusual placement but front-loads the single most decision-relevant fact, so it earns its position.

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?

The tool is simple (no params, no output schema), and the description covers cost and the payment handshake, but for a paywalled proxy it leaves the caller unsure what the post-payment payload looks like or how to follow up, which is the main thing an agent needs to plan a paid call.

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?

Zero parameters, so the baseline of 4 applies; the description introduces no parameter meaning that could conflict with the empty input schema.

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?

States a specific verb and resource: returns the top 200 X1 tokens with full metadata. The scope (top 200, X1 chain) is concrete enough to distinguish it from generic token listings, though it never names the sibling it differs from (e.g. top_tokens).

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?

The 'PAYWALLED' prefix and the $0.025 price imply this is a paid, last-resort path and that a free alternative likely exists, but the description never says when to use this over a free sibling or what preconditions the caller must meet. Usage must be inferred from the paywall framing.

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