Skip to main content
Glama
Coinversaa

Coinversaa Pulse

Official

market_recent_candles

Retrieve the most recent 1-minute candle history for any market. Analyze short-term intraday structure, momentum, and micro-pullbacks with up to 12 hours of data.

Instructions

Get recent 1-minute candle history for a market. Best for short intraday structure checks, recent momentum, and micro-pullback analysis. This MCP tool is intentionally capped to the most recent 12 hours so agents do not fetch huge minute-bar dumps in one call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
useToonFormatNoReturn data in compact toon format (default: true). Set to false for standard JSON.
symbolYesMarket symbol (e.g. BTC, ETH, SOL, xyz:GOLD, cash:TSLA)
limitNoNumber of 1-minute candles to return. Capped at 720 candles (12h) to keep MCP responses practical.

Implementation Reference

  • The handler function that executes the 'market_recent_candles' tool logic. It calls the API at `/pulse/market/candles/recent/{symbol}` with interval '1m' and the requested limit.
    // TOOL 28: Recent 1m Candles
    // ══════════════════════════════════════════════════════════
    if (shouldRegister("market_recent_candles")) server.registerTool(
      "market_recent_candles",
      {
        description: "Get recent 1-minute candle history for a market. Best for short intraday structure checks, recent momentum, and micro-pullback analysis. This MCP tool is intentionally capped to the most recent 12 hours so agents do not fetch huge minute-bar dumps in one call.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          symbol: z.string().min(1).max(20).describe("Market symbol (e.g. BTC, ETH, SOL, xyz:GOLD, cash:TSLA)"),
          limit: z.number().min(1).max(720).default(240).describe("Number of 1-minute candles to return. Capped at 720 candles (12h) to keep MCP responses practical."),
        },
      },
      async ({ useToonFormat, symbol, limit }) =>
        toolResult(await callAPI(useToonFormat, `/pulse/market/candles/recent/${normalizeCoin(symbol)}`, { interval: "1m", limit: String(limit) }))
    );
  • src/index.ts:942-954 (registration)
    Tool registration using `server.registerTool` with the name 'market_recent_candles', schema description, input validation (symbol, limit, useToonFormat), and the handler function.
    if (shouldRegister("market_recent_candles")) server.registerTool(
      "market_recent_candles",
      {
        description: "Get recent 1-minute candle history for a market. Best for short intraday structure checks, recent momentum, and micro-pullback analysis. This MCP tool is intentionally capped to the most recent 12 hours so agents do not fetch huge minute-bar dumps in one call.",
        inputSchema: {
          useToonFormat: useToonFormatSchema,
          symbol: z.string().min(1).max(20).describe("Market symbol (e.g. BTC, ETH, SOL, xyz:GOLD, cash:TSLA)"),
          limit: z.number().min(1).max(720).default(240).describe("Number of 1-minute candles to return. Capped at 720 candles (12h) to keep MCP responses practical."),
        },
      },
      async ({ useToonFormat, symbol, limit }) =>
        toolResult(await callAPI(useToonFormat, `/pulse/market/candles/recent/${normalizeCoin(symbol)}`, { interval: "1m", limit: String(limit) }))
    );
  • Input schema for the tool: 'useToonFormat' (boolean), 'symbol' (string, min 1 max 20), and 'limit' (number, min 1 max 720, default 240) for the number of 1-minute candles.
    {
      description: "Get recent 1-minute candle history for a market. Best for short intraday structure checks, recent momentum, and micro-pullback analysis. This MCP tool is intentionally capped to the most recent 12 hours so agents do not fetch huge minute-bar dumps in one call.",
      inputSchema: {
        useToonFormat: useToonFormatSchema,
        symbol: z.string().min(1).max(20).describe("Market symbol (e.g. BTC, ETH, SOL, xyz:GOLD, cash:TSLA)"),
        limit: z.number().min(1).max(720).default(240).describe("Number of 1-minute candles to return. Capped at 720 candles (12h) to keep MCP responses practical."),
      },
  • The compiled JavaScript version of the 'market_recent_candles' tool handler, calling the same API endpoint.
    // TOOL 28: Recent 1m Candles
    // ══════════════════════════════════════════════════════════
    if (shouldRegister("market_recent_candles"))
        server.registerTool("market_recent_candles", {
            description: "Get recent 1-minute candle history for a market. Best for short intraday structure checks, recent momentum, and micro-pullback analysis. This MCP tool is intentionally capped to the most recent 12 hours so agents do not fetch huge minute-bar dumps in one call.",
            inputSchema: {
                useToonFormat: useToonFormatSchema,
                symbol: z.string().min(1).max(20).describe("Market symbol (e.g. BTC, ETH, SOL, xyz:GOLD, cash:TSLA)"),
                limit: z.number().min(1).max(720).default(240).describe("Number of 1-minute candles to return. Capped at 720 candles (12h) to keep MCP responses practical."),
            },
        }, async ({ useToonFormat, symbol, limit }) => toolResult(await callAPI(useToonFormat, `/pulse/market/candles/recent/${normalizeCoin(symbol)}`, { interval: "1m", limit: String(limit) })));
Behavior4/5

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

With no annotations, the description carries full burden. It discloses the intentional 12-hour cap and explains it prevents large data dumps. However, it doesn't mention data freshness or whether the current incomplete candle is included.

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 sentences front-load purpose and constraint. Every word is meaningful with no redundancy. The structure is ideal for an AI agent.

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?

Given no output schema or annotations, the description covers purpose, usage, and behavioral constraints well. It could be more complete by briefly describing output fields (e.g., open, high, low, close, volume), but overall it's sufficient.

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?

Schema coverage is 100%, so baseline is 3. The description adds context about the limit's purpose (keeping responses practical) and hints at toon format, but does not significantly enhance understanding 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 explicitly states 'Get recent 1-minute candle history for a market', providing a specific verb ('get') and resource ('1-minute candle history'). This clearly distinguishes it from sibling tools like 'market_orderbook' and 'market_price'.

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?

The description says 'Best for short intraday structure checks, recent momentum, and micro-pullback analysis', offering usage context but no explicit when-not-to-use or alternatives. It lacks guidance on scenarios like longer timeframes or different data resolutions.

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/Coinversaa/mcp-server'

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