Skip to main content
Glama

get_recent_signals

Retrieve recent signal and order events with status, payload, target account, prices, slippage, and delivery latency; filter by magic, account, status, or date range.

Instructions

Müşterinin son sinyal/emir olaylarını (webhook + MCP) döner: tarih, durum (pending/done/rejected/failed/test), payload, hedef hesap; ayrıca sinyal fiyatı, dolum fiyatı, kayma (aleyhe +) ve iletim gecikmesi (sn). magic/hesap/durum/tarih ile süzülebilir.

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
limitNoKayıt sayısı (varsayılan 30)
magicNoYalnız bu magic'li sinyaller
sinceNoBu zamandan sonrası (ISO)
beforeNoBu zamandan öncesi (ISO, sayfalama)
statusNoDurum filtresi
accountIdNoYalnız bu hesaba giden sinyaller

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description bears the full behavioral burden. It does valuable work by disclosing the returned fields, including derived metrics (slippage noted as 'aleyhe +', latency in seconds) and the status vocabulary, but it never states that the operation is read-only, how pagination via 'before' behaves, or anything about result size limits beyond the schema.

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?

It is a single dense sentence, front-loaded with the resource, then the payload fields, then the filter options. The semicolon-separated field list is long but every item conveys return-value information that is otherwise unavailable since there is no output schema.

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

Completeness4/5

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

For a read-only, zero-required-parameter listing tool with full schema coverage but no output schema, the description adequately explains what data comes back and what can be filtered. The main gap is the absence of any statement about default page size or pagination semantics, which the schema only partially covers.

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 description coverage is 100%, so every parameter is already documented with defaults, formats and the status enum. The description only restates the filter dimensions (magic/account/status/date) without adding format, default or interaction rules, so the baseline 3 applies.

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 names a specific verb and resource ('son sinyal/emir olaylarını ... döner') and enumerates the returned fields (date, status, payload, target account, signal price, fill price, slippage, latency), which clearly separates it from siblings like get_trades or get_positions. It stops short of explicitly naming an alternative, so it does not reach a 5.

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?

Usage is implied by the tool name and the listed filters ('magic/hesap/durum/tarih ile süzülebilir'), so an agent can infer this is the tool for recent signal events. However, there is no explicit when-to-use or when-not-to-use statement and no routing to a sibling for historical or filtered trade data.

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