Recent crypto market-intelligence briefs from Liquid State — analyst write-ups on price action, liquidations, funding, and macro. Returns headline, category, coins, summary, url, publishedAt. Use when the user wants recent crypto news/analysis or what's moving markets.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | How many recent briefs to return (1-50, default 15). |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It describes the output fields (headline, category, coins, summary, url, publishedAt) and the default/range for limit. It does not mention side effects, but as a 'get' operation, it is clearly non-destructive. Lacks explicit mention of read-only or auth, but this is not misleading.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, with two sentences: one stating the purpose and output, the other giving usage guidance. It is front-loaded with the primary function and includes essential details without fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple nature of the tool (a get with one optional parameter), the description is complete. It lists the output fields, provides usage context, and specifies the parameter behavior. No output schema is provided, but the description covers what is returned.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The single parameter 'limit' is described with a clear meaning, valid range (1-50), and default value (15). The schema already documents the parameter, and the description adds useful constraints and default behavior.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves recent crypto market-intelligence briefs and lists the specific fields returned. It distinguishes itself from sibling tools by focusing on briefs/news rather than derivatives, guides, or market overview.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states when to use the tool: 'Use when the user wants recent crypto news/analysis or what's moving markets.' This provides clear guidance and implicitly differentiates it from sibling tools.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly distinct, but get_market_overview and get_market_state both return funding and price snapshots for BTC/ETH/SOL, with get_market_state adding OI, liquidations, and a regime signal. get_derivatives also overlaps with get_market_state on funding and open interest at the single-asset level, which could cause an agent to pick the wrong tool.
All six tools follow a consistent get_<resource> naming pattern with clear, descriptive nouns. There are no mixed casing styles, vague verbs, or inconsistent conventions.
Six tools is a well-scoped size for a crypto market intelligence server. Each tool has a distinct role in the set: news briefs, derivatives data, guides, market overview, market state, and track record.
The tool surface covers the core intelligence workflows well: recent analysis, derivatives data, market snapshots, educational content, and a verifiable track record. Minor gaps exist, such as no historical data endpoints and limited spot-price coverage beyond BTC/ETH/SOL, but agents can generally work around these.
