Skip to main content
Glama

Recent signals

get_recent_signals
Read-onlyIdempotent

/api/v1/feed: leader trades with gate and fill status; no since: the newest. TSV <=4 KB; json: the API body.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
sinceNoa feed seq; unset: newest
formatNo
walletNo0x wallets, slugs or 8-hex

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

C2.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description does add real behavioral context beyond that: the output can be TSV capped at 4 KB, or json returning the API body, which tells the agent about size limits and format differences. It still leaves undefined what "gate" and "fill status" mean and how results are ordered or paginated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loads the resource path, so an agent gets the core fact immediately. However, the telegraphic fragment style ("no since: the newest. TSV <=4 KB; json: the API body.") sacrifices readability and requires decoding rather than being crisply stated.

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?

For a read-only feed listing with no output schema, the description does sketch the returned content and the two output formats, which is the minimum an agent needs. It stops short of defining the returned fields, ordering, or how wallet/limit filter the feed, leaving meaningful gaps given 50% parameter coverage and no output schema.

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 coverage is 50%, with limit and format having no description. The description partially compensates by clarifying `since` (unset = newest) and by distinguishing the two `format` values (tsv vs json body), and the 4 KB note hints at output size constraints. It says nothing about `wallet` or how `limit` interacts with the size cap, so the gap is only partly filled.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the underlying resource (/api/v1/feed) and its contents (leader trades with gate and fill status), so an agent can infer this returns recent feed entries. But it never states an explicit verb like "retrieve"/"list" and relies on domain jargon ("gate and fill status") that may not be self-explanatory. It also does nothing to distinguish it from siblings such as get_trader or find_traders.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The only conditional guidance is "no since: the newest", which explains a default rather than when to choose this tool. There is no statement of when to use this versus get_trader, find_traders, or watch_traders, and no exclusions or prerequisites are given.

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