Skip to main content
Glama

crypto-prices

Server Details

Live USD crypto spot prices by ticker (BTC, ETH, SOL, …) for AI agents. x402 pay-per-call.

Status
Healthy
Last Tested
Transport
Streamable HTTP
URL
Repository
agishub/agishub-mcp
GitHub Stars
1
Server Listing
AgisHub MCP Server

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsA

Average 3.7/5 across 1 of 1 tools scored.

Server CoherenceA
Disambiguation5/5

With only one tool, there is no possibility for confusion. The tool's purpose is clearly defined and distinct.

Naming Consistency5/5

With a single tool, naming consistency is not applicable. The name 'price' is simple and descriptive.

Tool Count3/5

One tool is on the lower end of appropriate counts. It suffices for a simple price query server but offers no additional functionality.

Completeness4/5

The single tool covers the stated purpose of fetching USD spot prices for multiple cryptocurrencies, but lacks support for other currencies or historical data, which are minor gaps.

Available Tools

1 tool
priceAInspect

Get live USD spot prices for one or more cryptocurrencies by ticker symbol (e.g. BTC, ETH, SOL).

ParametersJSON Schema
NameRequiredDescriptionDefault
symbolsYesComma-separated ticker symbols, e.g. 'BTC,ETH,SOL'. Prices are returned in USD.
Behavior2/5

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'live USD spot prices' without revealing error handling, rate limits, or data freshness. As a simple query tool, it lacks transparency on what happens with invalid symbols or network issues.

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?

The description is a single, well-formed sentence that front-loads the key information: the action (Get), the resource (live USD spot prices), and the input format (ticker symbols with examples). Every word is necessary, and there is no extraneous content.

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

Completeness3/5

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

Given the simplicity of the tool (1 parameter, no output schema, no siblings), the description covers the basics of functionality and input requirements. However, it does not specify the return format or handling of multiple symbols, which would be useful for a complete understanding.

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?

The input schema already describes the 'symbols' parameter with 100% coverage: 'Comma-separated ticker symbols, e.g. 'BTC,ETH,SOL'. Prices are returned in USD.' The description reiterates this without adding new meaning, so it meets the baseline for high schema coverage but does not enhance it.

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 the tool's purpose: 'Get live USD spot prices for one or more cryptocurrencies by ticker symbol' with specific examples (BTC, ETH, SOL). The verb 'get' and resource 'live USD spot prices' are precise and unambiguous, making the tool's function immediately apparent.

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 implies usage for obtaining cryptocurrency prices, but does not explicitly provide when-to-use guidance or state alternatives. Since no sibling tools are listed, this is acceptable, but the description could be improved by noting that it only supports specific tickers or USD pricing.

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

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Servers

  • A
    license
    -
    quality
    C
    maintenance
    Provides real-time cryptocurrency pricing data and market information from major exchanges like Binance, Coinbase, and Kraken via the Luzia API. It enables AI assistants to fetch ticker prices, compare exchange rates, and analyze market trends through specialized tools and prompts.
    60
    MIT
  • A
    license
    A
    quality
    D
    maintenance
    Real-time crypto intelligence for AI agents. Technical analysis, liquidation heatmaps, sentiment, and funding rates for 50+ Hyperliquid perpetuals via x402 micropayments.
    15
    1
    MIT

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.