Skip to main content
Glama

Crypto pulse

crypto_pulse
Read-onlyIdempotent

Crypto market pulse. High-frequency 1-call crypto & perp squeeze heartbeat: fuses Fear & Greed, 5-exchange funding-rate squeeze extremes (Hyperliquid, Binance, Bybit, Bitget, Gate), and global DEX 24h volume into a single marketRegime signal. Free live board: https://apexfaucet.xyz/pulse/ . $0.001 per call over x402 or X-API-Key.

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

Input Schema

NameRequiredDescriptionDefault
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so the safety profile is covered. The description adds genuinely new context: the $0.001 per-call cost, the two auth paths (x402 payment signature or X-API-Key), and the exact upstream sources feeding the aggregate. It does not state rate limits or caching freshness, 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?

The core capability and the composite signal are front-loaded in the first two sentences, and the exchange list is informative rather than filler. The trailing promo link and price sentence are slightly sales-oriented but do carry decision-relevant cost information, so waste is minimal.

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?

For a zero-required-parameter aggregate call with no output schema, the description supplies what an agent needs: the data sources, the shape of the return (a single marketRegime signal), the cost, and the auth options. Only the response structure's detail and freshness/polling cadence are left unstated.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With one optional parameter at 100% schema description coverage, the schema already explains the x402 payment payload. The description adds the useful fact that an X-API-Key is an alternative to paying per call, which clarifies why the payment parameter is optional, but it adds no format or syntax detail.

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?

The description names a concrete verb-and-resource pairing: it fuses Fear & Greed, five named exchanges' funding-rate squeeze extremes, and DEX 24h volume into a single 'marketRegime' signal. That is far more specific than the title 'Crypto pulse'. It does not explicitly differentiate itself from siblings like market_pulse or crypto_fear_greed, so it falls short of a 5.

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?

Usage is implied by 'high-frequency 1-call ... heartbeat', which suggests cheap repeated polling, and the live board link offers a zero-cost alternative for one-off checks. However, there is no explicit statement of when to prefer this over market_pulse or crypto_fear_greed, and no exclusions or prerequisites beyond payment.

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