Skip to main content
Glama

Gemini Crypto

by io.github.pipeworx-io

Ticker V2

ticker_v2
Read-onlyIdempotent

Gemini crypto exchange v2 ticker with 24-hour rolling stats: open, high, low, last, changes, bid/ask, hourly closes. Use for daily summary on Gemini-listed pairs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
askNoCurrent ask price
bidNoCurrent bid price
lowNoLowest price in 24h
highNoHighest price in 24h
openNoOpening price for 24h period
closeNoClosing price
symbolNoTrading pair symbol
changesNoPrice changes

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint; description adds value by specifying '24-hour rolling stats' and 'hourly closes', which are behavioral details beyond the annotation flags.

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 succinct sentences: first defines what the tool does, second advises when to use. No unnecessary words, front-loaded with key information.

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?

Simple tool with 1 parameter, rich annotations, and an output schema (not shown). Description covers core functionality and usage context well; minor lack of parameter explanation is addressed under semantics. Adequate for the tool's simplicity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% (no param descriptions in schema). The tool description does not explain the 'symbol' parameter format or constraints; only an example in the schema indicates lowercase pair like 'ethusd'. This is a critical gap given the reliance on description for parameter semantics.

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?

Clear verb+resource: 'Gemini crypto exchange v2 ticker' with specific stats listed. Distinguishes from sibling 'ticker' by explicitly calling it v2, and states usage for daily summary on Gemini-listed pairs.

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?

Explicitly says 'Use for daily summary on Gemini-listed pairs', providing clear context. Does not mention when not to use or alternatives, but the context is sufficient given sibling tool names like 'ticker' and 'candles'.

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

All Gemini Crypto 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

A3.8/5.0
Disambiguation3/5

Many tools serve overlapping research purposes (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim, entity_profile, compare_entities), which could confuse an agent. However, descriptions help differentiate them by use case (single vs multi-part, grounded vs standard, etc.). Some overlap remains.

Naming Consistency3/5

Tool names mix patterns: some are verb_noun (ask_pipeworx, bet_research), others are noun_phrase (price_feed, recent_alerts) or adjective_noun (ticker_v2). No strong naming convention, but all use snake_case consistently, making them readable.

Tool Count3/5

40 tools is on the high side for a single server, covering both Gemini exchange data and Pipeworx's broad knowledge tools. While each tool serves a purpose, the scope feels broad, and some tools could be separated into dedicated servers.

Completeness4/5

The Gemini exchange tools cover essential read-only data (order book, candles, ticker, trades), but lack order placement, likely intentionally. The Pipeworx tools provide extensive research capabilities across many domains, leaving few gaps for the stated purposes.

Resources