Limitless MCP

get_recent_activity

Retrieve a unified feed of recent on-chain activity including trades, splits, merges, and redemptions across all markets with market names.

Instructions

Get a unified feed of all recent on-chain activity: trades, splits, merges, and redemptions across both market types with market names.

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

Input Schema

Name	Required	Description	Default
`first`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Mar 24, 2026

TDQS

B3.2/5.0

Behavior3/5

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

With no annotations provided, the description must carry the full disclosure burden. It successfully enumerates the specific activity types included (trades, splits, merges, redemptions) and mentions 'market names' are included. However, it fails to clarify what 'recent' means (time window), pagination behavior, or whether the feed is real-time vs cached.

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?

The description is a single dense sentence that efficiently conveys the tool's purpose and content types without redundancy. Every element serves to specify the scope or contents of the feed.

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?

Given the lack of output schema and annotations, the description adequately covers what data is returned (activity types and market names) but omits operational context like pagination mechanics, time range constraints for 'recent', and response structure that would be necessary for complete tool selection confidence.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single 'first' parameter, so the description must compensate. It fails to mention the 'first' parameter entirely, leaving undocumented what '30' represents (presumably result count/limit) and how pagination works.

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 clearly identifies the action ('Get'), resource ('unified feed'), and specific scope ('trades, splits, merges, and redemptions across both market types'). The terms 'unified' and 'across both market types' implicitly distinguish it from sibling tools like get_market_trades or get_trader_trades which likely target specific entities, though explicit differentiation is absent.

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 description implies usage through the word 'unified' (suggesting use when aggregating across markets), but provides no explicit when-to-use guidance or named alternatives. It doesn't clarify whether this should be preferred over get_liquidity_events or specific trade getters.

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

Deploy Server