Skip to main content
Glama

Racketeer Pre-Trade Checks (Solana)

signal track record

signal_track_record
Read-only

Public log of every experimental signal served, with timestamp, SHA-256 hash and 7-day outcome when known. Free.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds genuinely new behavior: entries are public, free, hash-stamped for verification, and outcomes are only present 'when known', warning the agent about incomplete data. It omits ordering and whether the log is paginated or unbounded, which matters for a 'log of every' signal.

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?

A single sentence, front-loaded with the resource, followed by the returned fields and the cost. Nothing is redundant and nothing important is buried.

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?

With no parameters, no output schema, and safety covered by annotations, the description carries the return-value burden and does so by naming timestamp, SHA-256 hash, and 7-day outcome. The only real gap is volume/ordering behavior for a log that claims to contain every signal.

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 tool takes zero parameters, so there is no parameter semantics to explain; baseline 4 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?

It names a specific resource — the public log of every experimental signal served — and lists what each entry contains, which implicitly separates it from the forward-looking siblings like signal_experimental. The retrieval verb is only implied ('log of...'), so it is clear but not crisply verb-first.

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?

It never states when to reach for this tool versus signal_experimental or signal_batch_experimental, nor any when-not condition. The mention of '7-day outcome' hints at an audit/verification use case, but that is inference, not guidance.

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