Skip to main content
Glama

PredMCP

by io.github.RavioleLabs

Get Recent Signals

get_recent_signals
Read-only

Server-detected events from the last hour: funding outliers (≥3x 7d baseline), whale trades (≥$100k), OI caps reached. Cursor-based — pass next_cursor back as since_id to receive only new events. The polling equivalent of the /sse/signals stream. Pro tool get_signal_history covers 7 days with forward-return outcomes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
coinNoFilter to one coin, e.g. "BTC"
limitNoMax events (free tier cap: 20)
since_idNoCursor from a previous call — returns only events with id > since_id. Omit on first call.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true. Description adds cursor mechanism, time window (last hour), and specific event filters, but doesn't detail pagination direction or empty response behavior.

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?

Three concise sentences with no fluff. Front-loaded with most important information (event types and time range).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 3 parameters and no output schema, the description is complete: it covers purpose, usage pattern, alternative tool, and pagination. No gaps.

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?

Schema coverage is 100% with basic descriptions. Description adds value by explaining since_id cursor usage and free tier limit cap, going beyond schema.

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?

Description explicitly states verb 'get' and resource 'recent signals', enumerates specific event types (funding outliers, whale trades, OI caps), and distinguishes from sibling tool get_signal_history.

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?

Provides clear cursor-based pagination instructions, mentions polling equivalent to /sse/signals stream, and explicitly contrasts with get_signal_history which covers 7 days with outcomes.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All PredMCP toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.7/5.0
Disambiguation3/5

Many tools are specialized, but several pairs have fuzzy boundaries: e.g., get_funding_rates vs get_top_funding_rates, get_basic_macro vs get_macro_context, get_simple_iv vs get_options_iv. An agent could easily select the wrong one.

Naming Consistency4/5

Most tools follow a 'get_X' pattern with descriptive noun phrases. There are a few exceptions like 'create_api_key' and 'search_markets', but overall the convention is consistent and readable.

Tool Count2/5

With 47 tools, the server is overloaded. While the domain is broad, this many tools makes discovery and selection difficult for an agent, reducing coherence.

Completeness5/5

The tool set covers an impressively wide range: macro data, funding, prediction markets, OI history, whale tracking, risk analytics, position sizing, backtesting, and signal generation. It leaves no obvious gaps for a crypto trading assistant.

Resources