Skip to main content
Glama

Latest revealed signals

latest_signals
Read-onlyIdempotent

Signals recently detected and publicly revealed in Provyan's hash-chained ledger, with the call made at the time and the graded result once seven days have passed, plus the live hit record. Statistics about past price behaviour on Binance daily candles. Not financial advice and not a prediction.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds substantive context: the ledger is hash-chained (immutable/verifiable provenance), results only become 'graded' after seven days have passed, and the record includes live hits. It also disclaims financial advice and prediction, which sets expectations about interpretation of the output. Missing: how far back 'recently' reaches or how many signals are returned.

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?

The first sentence is dense but front-loads the important content. The second sentence about Binance daily-candle statistics is under-connected to the rest and reads like it was spliced in, creating ambiguity rather than value. The disclaimer clause is short and defensible, so the main waste is the orphaned statistics sentence.

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?

With no output schema, the description carries the burden of explaining returns, and it does name the constituent parts (original call, seven-day graded outcome, live hit record), which is reasonably complete. It falls short on operational specifics an agent needs: the definition of 'recently', the number of signals returned, and how the 'statistics' element relates to the signal records.

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?

The input schema declares zero parameters, so there is no parameter semantics to document and the baseline of 4 applies. The description correctly implies the tool takes no arguments and returns a fixed recent window rather than a caller-specified range.

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 identifies the resource (recently revealed signals in Provyan's hash-chained ledger) and enumerates the payload components: the call made at detection, the graded result after seven days, and the live hit record. However, there is no clear verb (retrieve? list?) and the second sentence — 'Statistics about past price behaviour on Binance daily candles' — sits awkwardly, leaving ambiguity about whether the tool returns signals, statistics, or both. It never distinguishes itself from the named siblings such as list_coins_and_signals.

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?

There is no statement of when to call this tool, no prerequisites, and no mention of alternatives. An agent is left to infer from the name that this is the 'recent' counterpart to a historical or search tool, but nothing in the text confirms that or routes it away from list_coins_and_signals or find_evidence.

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