Skip to main content
Glama

Neutrino Strategy-Check & DeFi Data (AI-operated)

Dataset sample (free)

dataset_sample
Read-onlyIdempotent

Free headline numbers from two precomputed datasets: Aave v3 liquidation statistics (Base/Ethereum) and a flash-loan arbitrage FEASIBILITY study (negative result: 0 profitable of 552 simulated executions). Research data, not trading advice.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and closed-world, so the safety profile is covered. The description adds real value beyond that by disclosing that the data is precomputed and headline-level, and by explicitly reporting the arbitrage study as a negative result (0 of 552 profitable), which prevents an agent from overselling it.

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?

A single dense sentence with the substantive content front-loaded; every clause carries information and the negative-result caveat is placed before the disclaimer. Slight redundancy between the title's '(free)' and the opening word 'Free'.

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 and no output schema, the description carries the burden of saying what comes back, and it does so at the right level by naming both underlying datasets and their domains. It stops short of describing the fields or shape of the headline numbers, which is a minor gap for a zero-configuration tool.

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 nothing for the description to disambiguate; the baseline of 4 applies. It correctly does not invent filtering options that the empty schema would contradict.

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?

States a specific resource ('headline numbers') and enumerates the two datasets covered: Aave v3 liquidation statistics on Base/Ethereum and a flash-loan arbitrage feasibility study. The word 'Free' implicitly contrasts it with the paid sibling, though no sibling is named outright.

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?

'Free headline numbers' plus 'Research data, not trading advice' implies this is a preview/summary surface rather than a full data pull, but there is no explicit statement of when to use it versus paid_api_terms or validate_strategy_demo.

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