Skip to main content
Glama

Gemini Crypto

by io.github.pipeworx-io

Symbol Details

symbol_details
Read-onlyIdempotent

Fetch trading pair metadata from Gemini for a symbol: base/quote currency, tick size, quote increment, min order size, and status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
statusNoTrading pair status
symbolNoTrading pair symbol
tick_sizeNoMinimum price increment
wrap_enabledNoWhether wrapping is enabled
base_currencyNoBase currency code
min_order_sizeNoMinimum order size
quote_currencyNoQuote currency code
quote_incrementNoMinimum quote currency increment

TDQS

A3.6/5.0
Behavior3/5

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

Annotations indicate read-only, idempotent, non-destructive. Description adds that it 'fetches metadata' which is consistent. No extra behavioral context beyond annotations, but annotations already provide safety profile.

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?

One sentence efficiently conveys purpose and output fields. No wasted words.

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?

With output schema present, description adequately covers tool purpose. Could mention that symbol must be active on Gemini, but overall complete for a simple read operation.

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?

Single parameter 'symbol' with example 'btcusd' gives some context, but no format details or allowed values. Schema coverage is 0%, so description partially compensates but lacks depth.

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?

Description clearly states the verb 'Fetch', the resource 'trading pair metadata from Gemini', and lists specific fields returned (base/quote currency, tick size, etc.). It distinguishes from sibling tools like ticker or candles which return different data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives (e.g., ticker for price, candles for OHLC). No explicit conditions or exclusions mentioned.

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