Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_weekend_liquidity

Check if crypto liquidity is thin right now, such as on weekends or off-hours. Returns weekend status, session, 0-100 liquidity score and a verdict from the UTC clock, with no market data needed.

Instructions

Use when the user asks whether crypto liquidity is thin right now, e.g. on a weekend or in off-hours. Returns is_weekend, is_low_liquidity, the session, a 0-100 liquidity score and a verdict, from the UTC clock (no market data). Ex: no parameters Costs $0.005 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the burden and does well: it discloses the data source ('from the UTC clock (no market data)'), so the agent knows this is a computed heuristic rather than a live market read, and it discloses the price ('Costs $0.005 USDC per call'). It omits the exact thresholds behind is_low_liquidity and the 0-100 score, which would be helpful for interpreting borderline results.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The trigger is front-loaded and most sentences earn their place, but the tail collapses into an unpunctuated run-on ('Ex: no parameters Costs $0.005 USDC per call.') that muddles two unrelated facts. The abbreviation 'Ex:' is also unclear.

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

Completeness4/5

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

For a simple, zero-param indicator with no output schema, the description supplies the trigger, the returned fields, the data source and the cost, which is nearly everything needed. Only the scoring/threshold semantics behind the verdict are left unexplained.

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?

This is a zero-parameter tool, so the baseline is 4 and there is nothing to mis-document; the description confirms 'no parameters'. It loses the extra point only because the confirmation is tacked on in a mangled fragment rather than stated cleanly.

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?

The description states a specific purpose: telling the agent whether crypto liquidity is thin based on the UTC clock, and enumerates the outputs (is_weekend, is_low_liquidity, session, 0-100 score, verdict). It implicitly differentiates itself from clock/session siblings by framing the answer as a liquidity verdict rather than a raw session label, though it never names an alternative.

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?

It gives an explicit trigger ('Use when the user asks whether crypto liquidity is thin right now, e.g. on a weekend or in off-hours'), which is enough for an agent to route correctly. It does not state when NOT to use it or name which sibling to prefer for session data, so it falls short of a 5.

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