aim-network-m2m-hub

get_sentiment_signals

Multi-source market sentiment, orderflow & action signals ($0.02 USDC via x402 on Base). Endpoint: https://johngarp.click/api/v1/sentiment-signals

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

Input Schema

Name	Required	Description	Default
`payment_proof`	No	Optional Base Mainnet (Chain ID 8453) USDC transaction hash to recipient 0x1bbae07abebbb61f611391e02e81ee26b0c47b79, or a 24h VIP Pass tx_hash.

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose two important behaviors: the $0.02 USDC charge via x402 on Base and the concrete endpoint URL. It does not say what happens when payment_proof is omitted (402 challenge? free tier?), whether payment is per-call or reusable, or any rate limits, leaving the payment flow only half explained.

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?

Two compact fragments, zero filler, with the capability and the payment/endpoint details front-loaded. It is efficient, though the endpoint URL is arguably operational detail rather than selection guidance.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema, so the description must describe what a caller receives, and it does not: no payload shape, no freshness/update cadence, no signal field semantics. For a paid tool with an opaque optional payment parameter and no annotations, this leaves the agent unable to predict the result before spending USDC.

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?

Schema coverage is 100% and the payment_proof description already covers chain ID, recipient address and VIP pass hashes. The description adds only the price and x402/Base context, which is useful but marginal against an already complete schema, so baseline 3 applies.

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?

Names the resource content concretely: multi-source market sentiment, orderflow and action signals, plus the paid endpoint. An agent can tell it is a market-signal feed, but there is no verb and no explicit differentiation from close siblings like get_crypto_pulse or get_multi_source_dossier.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance, no exclusions, and no routing to alternatives among the seven sibling market-data tools. The only implied usage cue is the price, which hints this is a premium call but does not say when it beats the free teaser.

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

All aim-network-m2m-hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?