NythosX Market Data

get_track_record

Graded accuracy of every published signal bias: hit rate by confidence, bias and symbol, Wilson intervals, Brier score, independent samples (free, cached 15 min, one full report per call — no pagination). Omit symbol for the all-symbols report; pass it to filter to one instrument. Check this before paying for get_signal_bias, to see whether its track record supports trusting the call. Returns 404 if nothing has been graded yet for that filter.

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

Input Schema

Name	Required	Description	Default
`symbol`	No	Instrument symbol

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 20, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Since no annotations were provided, the description carries the entire burden of behavioral disclosure. It includes key operational constraints like caching time ('cached 15 min'), scope limitations ('one full report per call — no pagination'), and specific error handling ('Returns 404 if nothing has been graded').

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?

Despite its high information density, the description is structured efficiently. It identifies the core content first, then addresses limits/caching, and finishes with the usage context/error handling in a logical flow.

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?

Given the complexity of a financial analysis tool, this definition is exceptionally complete. It covers input behavior, output limitations (no pagination), and the tool's value proposition relative to similar tools.

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?

While the schema defines the types of symbols, the description clarifies the required *behavior* of the symbol parameter. Specifying that the symbol should be omitted for an 'all-symbols report' adds critical operational meaning that the schema alone cannot convey.

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 is extremely specific, detailing exactly what metrics are provided ('hit rate', 'Brier score', 'Wilson intervals') and what subject matter it covers ('Graded accuracy of every published signal bias'). This leaves no doubt about the tool's function.

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?

It provides critical comparative guidance, advising the user to check the tool before engaging with the related sibling tool ('get_signal_bias'). Furthermore, it defines the usage pattern for an 'all-symbols report' (omit symbol).

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

All NythosX Market Data tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?