Skip to main content
Glama

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

Paid endpoints and x402 payment terms

paid_api_terms
Read-onlyIdempotent

Returns the URLs, methods, prices and x402 payment terms (USDC on Base) of the full paid endpoints: POST /v1/validate ($0.10), GET /v1/liquidations ($0.01), GET /v1/flashloans ($0.02). Call those over HTTP with an x402 client; this MCP server does not take payment.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Beyond the readOnly/idempotent/closed-world annotations, it discloses the critical operational trait that payment is not handled here and must go through an external x402 client, plus the settlement currency and network (USDC on Base). It does not describe response shape or any rate/limit behavior, so it is strong but not exhaustive.

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?

Two sentences, front-loaded with the return payload and then the operational constraint, with the endpoint list packed into a single readable clause. No filler or redundant restatement of the title.

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?

For a no-parameter, read-only metadata tool with no output schema, the description covers what is returned (URLs, methods, prices, terms), for which endpoints, and how the agent should act on it. Nothing an agent needs to invoke it correctly is missing.

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 no parameters, so there is nothing for the description to disambiguate; the baseline for a zero-parameter tool applies. The endpoint and pricing detail is extra context rather than parameter semantics.

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 opens with a specific verb and resource ('Returns the URLs, methods, prices and x402 payment terms') and then enumerates the exact endpoints and prices, so an agent knows precisely what comes back without opening anything else.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It clearly directs the agent to call the listed endpoints over HTTP with an x402 client and states that this MCP server does not take payment, which is strong when-to-use/when-not guidance. It stops short of naming the sibling tools (dataset_sample, validate_strategy_demo) as alternatives, so routing among the catalog is left to inference.

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