Skip to main content
Glama
Sign In
Crypto News Sentiment (x402)

Crypto News Sentiment (x402)

by whatevercat-creator
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Price Quote

price_quote
Read-onlyIdempotent

Fetches the live x402 price of a crypto_sentiment call from an unpaid 402 response, letting you confirm payment requirements before funding a wallet.

Instructions

Free: the live x402 price of one crypto_sentiment call, read from an
unpaid request's 402 response. Nothing is signed; no wallet needed.

When not to use it: prices are fixed at $0.01 per crypto_sentiment call
and $0.05 per get_hourly_history call, so there's no need to call this
before every paid call. Use it to confirm the live price and payment
requirements, e.g. before funding a wallet. It quotes crypto_sentiment
only.

symbol must be exactly one of the 24 uppercase tickers from
list_supported_coins; lowercase or any other symbol is rejected by the
input schema before a request is sent. A low-coverage coin still gets a
quote; a crypto_sentiment call for it may then be refused with
"insufficient recent news" (not charged).

Input Schema

NameRequiredDescriptionDefault
symbolYesUppercase crypto ticker, one of the 24 from list_supported_coins (e.g. BTC). Stock tickers and other symbols are refused and not charged.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.4
    • addedInput schema / properties / symbol / description
      Added value: +"Uppercase crypto ticker, one of the 24 from list_supported_coins (e.g. BTC). Stock tickers and other symbols are refused and not charged."
    • addedInput schema / properties / symbol / enum
      Added value: +[
+  "BTC",
+  "ETH",
+  "SOL",
+  "XRP",
+  "DOGE",
+  "ADA",
+  "AVAX",
+  "LINK",
+  "MATIC",
+  "DOT",
+  "SHIB",
+  "LTC",
+  "BNB",
+  "USDC",
+  "USDT",
+  "NEAR",
+  "HYPE",
+  "QNT",
+  "AAVE",
+  "TAO",
+  "PEPE",
+  "PUMP",
+  "ENA",
+  "STRK"
+]
  2. First observedv0.1.2

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds meaningful context beyond those annotations: nothing is signed, no wallet is needed, quotes are free, low-coverage coins still get a quote, and a subsequent crypto_sentiment call may be refused without charge. These are exactly the behavioral details an agent needs for a price-probing tool.

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?

The description is front-loaded with the core purpose, immediately followed by exclusions, usage guidance, and validation caveats. Every sentence contributes operational information, and there is no filler or repetition.

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?

Given that an output schema exists, the description does not need to explain return values. It still covers the important complexities of this tool: free access, no signing, fixed pricing rationale, symbol validation, and low-coverage refusal behavior. The definition is complete for correct invocation.

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?

Schema coverage is 100% and the enum already lists the 24 valid uppercase tickers. The description still adds value by stating that lowercase symbols are rejected by the input schema before a request is sent, that quotes come from list_supported_coins, and that low-coverage coins may still be quoted even if a later call is refused. This goes beyond the schema without fully redefining the parameter.

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 states a specific verb and resource: it returns the live x402 price of one crypto_sentiment call from an unpaid 402 response. It also explicitly limits scope to crypto_sentiment and rules out wallet signing, making it clearly distinguishable from sibling tools like crypto_sentiment and get_hourly_history.

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?

It gives explicit when-not-to-use guidance ('no need to call this before every paid call') and when-to-use guidance ('use it to confirm the live price and payment requirements, e.g. before funding a wallet'). It also names list_supported_coins as the source of valid tickers, leaving little ambiguity.

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

Deploy Server

Other Tools