Skip to main content
Glama

snowsignals

by io.snowsignals

get_phase

Read-only

Get the current market phase for one coin, across a timeframe. This is a paid call. Set kind to 'boundary' for the reading from the last closed bar, which is settled and won't change, or 'updates' for the live reading still forming inside the current bar. Leave tf off, or set it to 'all', for every timeframe.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tfNoTimeframe; omit or 'all' for every enabled timeframe.
kindYes'boundary' = the settled reading from the last closed bar; 'updates' = the live reading still forming in the current bar.
currencyYesThe currency to classify. Call list_phase_meta for the enabled set.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses that this is a paid call and explains the stability difference between the settled 'boundary' reading and the still-forming 'updates' reading. This is valuable behavioral context that annotations alone do not provide.

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?

Three tightly written sentences with no filler. The main purpose is front-loaded, followed by the most important behavioral caveat (paid call) and then precise parameter instructions.

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

Completeness5/5

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

For a low-complexity read-only tool, the description covers the essential decisions: which kind to request, how to select timeframes, and that the call is paid. With annotations carrying the read-only safety profile and the schema covering parameters, nothing critical is missing for correct invocation.

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 description coverage is 100%, so the schema already documents currency, kind, and tf. The description repeats and reinforces the kind and tf semantics, but does not add substantial new meaning beyond what the schema provides.

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 clearly states a specific verb ('Get') and resource ('current market phase for one coin, across a timeframe'), and the scope 'one coin' distinguishes it from sibling list tooling like list_phase_meta and compose_phases. The kind/tf semantics further pin down exactly what the tool returns.

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?

The description gives detailed operational guidance: when to use 'boundary' versus 'updates', and how to handle 'tf' for all timeframes. It does not explicitly name alternatives or say when not to use this tool, but the context is clear enough for an agent to select it appropriately.

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

All snowsignals toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

Each tool has a distinct role: account/billing tools (balance, usage, notifications, deposit poll) are clearly separated from market-data tools (single phase, batch phases, phase metadata, phase stats). Even get_phase and compose_phases are differentiated by single-coin/single-timeframe vs multi-coin/multi-timeframe, and the descriptions make that boundary explicit.

Naming Consistency4/5

Most tools follow a get_ or verb_noun pattern (get_balance, get_phase, get_usage, compose_phases, deposit_poll), but 'phase_resolution_stats' breaks the pattern by lacking a verb, and 'compose_phases' vs 'get_phase' uses different verbs for closely related operations. The naming is still readable and predictable overall.

Tool Count5/5

Eight tools is well-scoped for this server: four handle the paid signal-reading workflow and four handle account/billing support around it. There are no redundant or throwaway tools, and each one earns its place.

Completeness5/5

The server covers the full workflow: discover what phases exist and pricing (list_phase_meta), get current readings (get_phase/compose_phases), interpret them (phase_resolution_stats), and manage the prepaid account (get_balance, get_usage, get_notifications, deposit_poll). No obvious dead ends or missing operations for the stated purpose.

Resources