Skip to main content
Glama

newsgurus-intel

by io.github.CollectorGuru

get_satoshi_moves

[$0.05 per call] News Gurus Intel API — dormant/Satoshi-era BTC wallet movement feed: on-chain moves with BTC amount, years dormant and transaction timestamps (public on-chain — no upstream-license restriction). Optional ?limit= (default 25, cap 50). Educational data, not financial advice. HOW TO PAY: an x402-capable client settles the payment challenge automatically (USDC on Base, no account needed); wallet-less clients pass a subscriber API key instead (Authorization: Bearer , X-API-Key header, or ?api_key= query) for calls within their plan. Browse every tool + price first with the FREE get_catalog tool.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo

TDQS

A4.3/5.0
Behavior4/5

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

The description transparently states that the data is educational and not financial advice, and includes payment settlement details. It does not mention any side effects or data freshness, but as a read-only feed, this is sufficient.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose, including extensive payment instructions that may be redundant across similar tools. While it packs necessary information, it could be more succinct without losing clarity.

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?

The description covers the data fields returned (BTC amount, years dormant, timestamps) and includes payment context, making it complete enough for an agent to understand the tool's output and usage without additional schema details.

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

Parameters5/5

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

The only parameter, limit, is clearly explained with its default (25) and cap (50). The description fully covers the parameter's meaning and constraints, exceeding the schema's minimal information.

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 clearly states the tool's function: a feed of dormant/Satoshi-era BTC wallet movements, specifying the data fields (BTC amount, years dormant, timestamps). It is distinct from other tools by focusing on Bitcoin wallet activity.

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?

The description provides usage details such as the optional limit parameter with default and cap, and mentions the educational nature. While it does not explicitly contrast with sibling tools, the specificity of the data makes the use case clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All newsgurus-intel toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation5/5

Every tool targets a unique resource or data feed, from agent status and macro snapshots to Polymarket whale analytics and MLB props. There is no overlap or ambiguity between tools, even those within the same domain (e.g., the multiple Polymarket tools are clearly distinguished by their focus on landscape, stats, new wallets, leaders, and flagged whales).

Naming Consistency5/5

The naming follows a consistent get_<resource> pattern for all 35 data retrieval tools, with only verify_memecoin deviating but still using a clear verb-noun structure. The pattern is uniform and predictable, making it easy for an agent to infer the purpose of any tool.

Tool Count2/5

With 36 tools, this significantly exceeds the typical well-scoped range of 3-15. While the server covers a broad range of market intelligence domains, the sheer number of tools makes navigation and selection challenging for an agent, placing it in the 'too many' category.

Completeness4/5

The API provides comprehensive coverage across signals, sentiment, on-chain data, institutional activity, sports, and macro, with both broad aggregate tools and per-symbol/asset specifics. Minor gaps exist, such as a lack of direct news headlines or a fear-greed index, but these are not critical dead ends given the stated purpose of delivering derived intelligence.

Resources