Skip to main content
Glama

xsignal

by io.github.philpof102-svg
OverviewAdmin

get_intent

FLAGSHIP. An outcome-priced momentum verdict that ABSTAINS below your confidence bar - the only x402 signal that refuses to answer (honestly) when it is not sure. Post {addr, min_confidence 0-1} then pay $0.01, and get a mechanical momentum verdict "gaining" or "fading" IF the signal agreement clears your bar, else a calibrated "abstain". Paid answers carry a keyless tamper-evidence receipt. confidence is a transparent heuristic, NOT a prediction; not financial advice. x402-paid at GET/POST /intent (3 free calls per wallet via ?wallet=0x…). Example: GET /intent?addr=0x4ed4E862860beD51a9570b96d89aF5E1B0Efefed&min_confidence=0.7

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
addrYes0x Base token address to read momentum for
questionNooptional free-text label / social query; defaults to the token symbol
min_confidenceNo0-1; abstain (no verdict, you still pay the flat fee) if mechanical confidence is below this. Default 0.6

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed5 schema fields changed
    • addedInput schema / properties / addr / description
      Added value: +"0x Base token address to read momentum for"
    • removedInput schema / properties / max_price
      Removed value: -{
-  "type": "number"
-}
    • addedInput schema / properties / min_confidence / description
      Added value: +"0-1; abstain (no verdict, you still pay the flat fee) if mechanical confidence is below this. Default 0.6"
    • addedInput schema / properties / question / description
      Added value: +"optional free-text label / social query; defaults to the token symbol"
    • addedInput schema / required
      Added value: +[
+  "addr"
+]
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations, the description fully discloses behavior: it is a paid, outcome-priced endpoint that returns 'gaining', 'fading', or 'abstain', provides a tamper-evidence receipt, and clarifies it's a heuristic, not financial advice. No hidden destructive or reading side effects are implied.

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 description is dense but front-loaded with the flagship label and key differentiator. Every sentence adds value, though the first sentence could be slightly tighter. Well-structured for an AI agent.

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 no output schema and moderate complexity, the description covers return values ('gaining', 'fading', 'abstain'), receipt, pricing (3 free calls, $0.01), and confidence semantics. No obvious gaps.

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%, baseline 3. The description adds meaningful semantics: it explains the role of min_confidence (causes abstain if below threshold), defines 'addr' as base token address, and clarifies 'question' defaulting to symbol. This goes beyond the schema descriptions.

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 verb ('get') and resource ('intent'), and distinguishes this tool from siblings as the only x402 signal that can abstain. It provides a specific purpose: yield a momentum verdict with confidence threshold.

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 explains when to use: to obtain a momentum verdict with a confidence bar, and gives an example. It omits explicit when-not-to-use or alternatives, but the abstain behavior implicitly differentiates from siblings.

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

All xsignal 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.

Resources