Skip to main content
Glama
SwapHunt crypto market context

SwapHunt crypto market context

Official

get_trading_session

Identify the active crypto trading session and its typical volatility from the UTC clock, returning overlap, minutes left, and the next session's volatility multiplier.

Instructions

Use when the user asks which trading session is active or how volatile this time of day usually is. Returns the session (Asian, London, New York, Off-hours), overlap, minutes left, the next session and its typical volatility multiplier, from the UTC clock. 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_trading_session"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/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 full behavioral burden and does reasonably well: it implies a computed, side-effect-free lookup ('from the UTC clock'), spells out the return contents, and discloses the cost of $0.005 USDC per call. It does not discuss auth, rate limits, or failure cases, which keeps it out of the top band.

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?

Three tight sentences, front-loaded with the usage trigger before the return contract and cost. The only minor inefficiency is 'Ex: no parameters', which restates something the schema already makes obvious.

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?

There is no output schema, so the description must describe return values itself, and it does so by listing every meaningful field. For a simple, parameterless lookup this is close to complete, with only minor ambiguity about the exact form of 'overlap' and 'minutes left'.

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 sits at 4, and the description confirms that explicitly with 'Ex: no parameters', matching the empty input schema. There is no parameter nuance left to explain.

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 gives a specific verb (returns) and resource (the trading session) and even enumerates the concrete fields returned: session name, overlap, minutes left, next session and its volatility multiplier. It is clearly distinguishable from siblings like get_alt_season or get_volatility, though it never names an alternative to explicitly contrast with.

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 opens with an explicit triggering condition: 'Use when the user asks which trading session is active or how volatile this time of day usually is.' That covers the two main intents well. There is no when-not guidance and no alternative tool is named, so it stops 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.