get_priceCurrent aggregated price for one or more symbols, computed from multiple exchange feeds.
| Name | Required | Description | Default |
|---|---|---|---|
| vs | No | Quote currency, default "usd" | |
| symbols | Yes | Single symbol or array of symbols (e.g. "btc" or ["btc","eth"]) |
| Name | Required | Description | Default |
|---|---|---|---|
| count | Yes | ||
| prices | Yes | ||
| timestamp | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Output schema / properties / countAdded value: +{
+ "type": "integer"
+}Output schema / properties / prices / items / properties / currencyAdded value: +{
+ "description": "ISO 4217 currency code the price is denominated in",
+ "type": "string"
+}Output schema / properties / prices / items / properties / maxAdded value: +{
+ "description": "Highest provider price after outlier filtering",
+ "type": "number"
+}Output schema / properties / prices / items / properties / medianAdded value: +{
+ "description": "Median provider price",
+ "type": "number"
+}Output schema / properties / prices / items / properties / minAdded value: +{
+ "description": "Lowest provider price after outlier filtering",
+ "type": "number"
+}Output schema / properties / prices / items / properties / priceAdded value: +{
+ "description": "Aggregated price in `currency` (default USD)",
+ "type": "number"
+}Output schema / properties / prices / items / properties / priceUsdRemoved value: -{
- "description": "Aggregated USD spot price",
- "type": "number"
-}Output schema / properties / prices / items / properties / providersAdded value: +{
+ "description": "Number of providers included in the aggregation",
+ "type": "integer"
+}Output schema / properties / prices / items / properties / symbol / descriptionPrevious value: -"Coin symbol queried"New value: +"Coin symbol"Output schema / properties / prices / items / properties / timestampAdded value: +{
+ "description": "ISO-8601 timestamp of the aggregation",
+ "type": "string"
+}Output schema / properties / prices / items / properties / updatedAtRemoved value: -{
- "description": "ISO-8601 timestamp of the price aggregation",
- "type": "string"
-}Output schema / properties / prices / items / requiredPrevious value: -[
- "symbol",
- "priceUsd"
-]New value: +[
+ "symbol",
+ "price",
+ "currency",
+ "providers",
+ "min",
+ "max",
+ "median",
+ "timestamp"
+]Output schema / properties / timestampAdded value: +{
+ "type": "string"
+}Output schema / requiredPrevious value: -[
- "prices"
-]New value: +[
+ "prices",
+ "count",
+ "timestamp"
+]Output schema / (root)Previous value: -nullNew value: +{
+ "additionalProperties": true,
+ "properties": {
+ "prices": {
+ "items": {
+ "additionalProperties": true,
+ "properties": {
+ "priceUsd": {
+ "description": "Aggregated USD spot price",
+ "type": "number"
+ },
+ "symbol": {
+ "description": "Coin symbol queried",
+ "type": "string"
+ },
+ "updatedAt": {
+ "description": "ISO-8601 timestamp of the price aggregation",
+ "type": "string"
+ }
+ },
+ "required": [
+ "symbol",
+ "priceUsd"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ }
+ },
+ "required": [
+ "prices"
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive nature, covering basic safety and idempotency. The description adds 'computed from multiple exchange feeds' but does not disclose behavioral details like caching, staleness, or the fact that additionalProperties are allowed in the input schema, which could affect tool invocation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence, directly states purpose and key differentiator (aggregated from multiple feeds). No wasted words, front-loaded with the most important information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity, full schema coverage, and presence of output schema, the description is complete. Annotations provide safety context, and the description adds the aggregation nuance. No missing information needed for safe and correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
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 both parameters thoroughly. The description adds no new information about parameter values or usage beyond restating the tool's purpose. Baseline 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool provides current aggregated price for one or more symbols from multiple exchange feeds. It distinguishes from siblings like get_price_by_symbol (single symbol) and get_coin (more data) by emphasizing aggregation and multiple exchange sources.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No explicit guidance on when to use this tool vs siblings (e.g., when to prefer get_price_by_symbol or get_rates). The description only states what it does, leaving the agent to infer usage context from the tool name and sibling list.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct aspect of cryptocurrency data: coin metadata, prices, rates (current, historical, changes), earn products, market summaries, stablecoin analysis, and symbol resolution. The detailed descriptions clearly differentiate even similar tools like get_price and get_price_by_symbol, or get_rates and list_earn_products.
All names use snake_case, but conventions vary: some are verb_noun (get_coin, list_coins, resolve_symbol), some are noun_noun (coin_history, fear_greed_index, market_summary), and some include 'by' for parameters. This mix is readable but could be more consistent.
With 21 tools, the server covers a broad domain of cryptocurrency data without being overwhelming. Each tool serves a clear purpose, and the count is appropriate for a comprehensive data API.
The tool set covers nearly all expected operations for a crypto data server: coin listing, metadata, prices, historical data, rates, yield products, market stats, top coins, stablecoin analysis, and symbol resolution. No obvious gaps are present for the stated focus on price, rate, and yield data.