Skip to main content
Glama

Kristo Intelligence — Base DeFi Signals (x402)

get_onchain_sales

Read-onlyIdempotent

Read-only operation — no side effects, no parameters. Returns the real on-chain payment history to this service's fee receiver on Base: total_volume_usd, total_sales, by_token, up to 100 history rows (tx hash, payer, amount, block, timestamp), source="real_blockchain", plus the wallet state and a market snapshot. Use it when you need provable revenue or settlement evidence; use get_market_stats for prices and get_bot_status for integration health.

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

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the opening 'read-only, no side effects' line is largely redundant. What the description adds beyond annotations is useful: the data source marker source="real_blockchain", the 100-row history cap, and the fact that wallet state and a market snapshot ride along — behavior an agent could not infer from the structured fields.

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?

Front-loads the read-only nature and the payload contents before the routing sentence, so an agent scanning the first clause already knows what it gets. It is dense but every clause carries information; the only mild waste is restating the read-only/no-side-effects trait already in annotations.

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?

There is no output schema, and the description compensates by enumerating the returned fields, the row limit, the source marker, and the auxiliary wallet/market data. Minor gaps remain — freshness or update cadence and whether the 100-row cap is a hard truncation — but an agent has enough to call it correctly.

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, which is the baseline-4 case; the description correctly reinforces that nothing needs to be supplied ('no parameters'). No further parameter meaning is required or missing.

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?

States a specific verb and resource: reads real on-chain payment history to the service's fee receiver on Base. It enumerates the returned fields (total_volume_usd, total_sales, by_token, history rows) so the agent knows exactly what this tool yields versus a generic stats tool.

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?

Gives an explicit selection rule: use this for provable revenue or settlement evidence, use get_market_stats for prices, get_bot_status for integration health. Two concrete alternatives are named with the conditions that select them, leaving little 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