Skip to main content
Glama

Trade signal & analysis

trade_signal

Generate a composite trade signal for major assets by analyzing price, derivatives positioning, and sentiment. Not investment advice.

Instructions

Composite trade signal for a major asset, combining price, derivatives positioning and sentiment. NOT investment advice.

PAID TOOL: up to $0.02 USDC per call (x402 on Base). Paid automatically from your configured wallet.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesAsset symbol (BTC, ETH, SOL...).
Behavior4/5

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

Discloses composite nature, non-investment advice status, and cost (up to $0.02/call). Without annotations, it provides key behavioral traits (read-only implied, paid). Could mention read-only explicitly.

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?

Two concise sentences plus a cost notice. Front-loaded with purpose. No wasted words.

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

Completeness3/5

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

Given one parameter and no output schema, description covers purpose and cost but lacks detail on output format (e.g., buy/sell/hold or numeric score) and update frequency. Adequate but not complete.

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?

Only parameter 'symbol' has schema description 'Asset symbol (BTC, ETH, SOL...).' The tool description adds no extra meaning beyond examples. Schema coverage is 100%, so baseline 3 is appropriate.

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?

Description states 'Composite trade signal for a major asset' with clear combination of price, derivatives, and sentiment. Distinguishes from sibling tools like meme_signal by specifying 'major asset' and from wallet_signal by focus on market data.

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?

Implied usage for major assets (symbols like BTC, ETH, SOL) but no explicit when-to-use or exclusion vs other data tools like token_momentum or token_price. Cost warning is included but not usage guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lucle87/boo-x402-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server