dydx-agent-gateway

Overview Schema Source Related Servers Discussions Admin

Latest Events

latest_events

Read-onlyIdempotent

Fetch anomaly events from dYdX detectors: funding_extreme, oi_spike_no_price, equity_jump, liq_cascade_signature. Filter by event kind or offset past the newest slice.

Instructions

Latest anomaly events from our detectors: funding_extreme, oi_spike_no_price, equity_jump, liq_cascade_signature. Each row: ts, kind, subject (ticker or address) and payload (dict of detector numbers). Optional kind filter; offset pages past the newest slice (events are pruned at 5000 — offset+limit beyond that returns []). Subscribe via webhooks/Telegram (alerts). Example: latest_events(limit=20, kind="funding_extreme")

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

Input Schema

Name	Required	Description	Default
`kind`	No
`limit`	No
`offset`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.3.0Sep 5, 2026

TDQS

A5/5.0

Behavior5/5

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

Beyond the readOnly/idempotent annotations, the description discloses the pruning limit, the exact return shape for offset+limit beyond the newest slice ([]), and that events are returned newest-first. No contradictions with annotations.

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?

The description is a tight paragraph: resource, row schema, filter semantics, pruning behavior, alternative subscription channel, and an example—all in five dense but efficient sentences. No filler.

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 simple read-only list tool with an output schema present, the description covers the core data, filtering, pagination edge cases, and alternative delivery mechanism. An agent has everything needed to invoke it correctly.

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

Parameters5/5

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

With 0% schema coverage, the description fully compensates: it defines 'kind' by listing the valid detector names, explains 'offset' as pagination past the newest slice, and 'limit' through the pagination semantics and a concrete example.

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?

The description opens with 'Latest anomaly events from our detectors' and names the four concrete event kinds, which makes the resource and scope unmistakable. It also defines the row structure (ts, kind, subject, payload), distinguishing it from the trading/market sibling tools.

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?

The description explains the optional kind filter, how limit and offset interact, and the pruning behavior at 5000 events. It also points to webhooks/Telegram for alert-style consumption, giving an explicit alternative to polling this endpoint.

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