Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

market-open-kit

[x402 paid: $0.040 USDC on Base] Trader morning kit in one call: BTC/ETH/SOL prices + Fear & Greed + Base gas + 10 crypto headlines. Everything needed to start the trading day. tools/call returns the live payment challenge.

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": "market-open-kit"
  }
}

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?

No annotations exist, so the description carries the full burden — and it discloses the two things an agent most needs: the exact price ($0.040 USDC on Base) and that tools/call returns a live payment challenge rather than data directly. It does not state read-only/idempotent semantics or caching/freshness behavior, which keeps it below a 5.

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 payment cost, then the payload, then the payment-flow note — a sensible order with no filler. Slight redundancy between 'Trader morning kit' and 'Everything needed to start the trading day' costs it a point.

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 output schema and no params, the description must enumerate what comes back, and it does so precisely (five named data points, headline count). The x402 payment-challenge behavior is also covered; only freshness/staleness and read-only semantics are left unstated.

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?

Zero parameters, so baseline is 4; there is nothing for the description to disambiguate. It correctly signals a no-argument call by framing the tool as a one-call bundle.

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 concrete verb+resource by enumerating the exact payload: BTC/ETH/SOL prices, Fear & Greed, Base gas, and 10 headlines in one call. An agent can tell this is an aggregate bundle distinct from the single-source siblings (base-gas, fear-greed, crypto-news), though it never names an alternative explicitly.

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?

'Everything needed to start the trading day' implies a morning/pre-market use case, but there is no explicit when-to-use versus when-not guidance and no sibling alternative named. The context is inferable rather than stated.

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