Skip to main content
Glama

truss44-mcp-crypto-price

by ai.smithery
OverviewDiscussionsAdmin

Get Exchanges

market-exchanges
Read-onlyIdempotent

Get top cryptocurrency exchanges ranked by 24h volume. Optionally pass an exchangeId (e.g. 'binance', 'coinbase') to get details for a specific exchange including volume, trading pairs, and market share.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoNumber of top exchanges to return when listing (1-50, default 10)
exchangeIdNoOptional: specific exchange ID to look up (e.g. 'binance', 'coinbase', 'kraken')

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
exchangesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed10 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • removedOutput schema / properties / exchanges / items / properties / percentTotalVolume / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / exchanges / items / properties / percentTotalVolume / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / exchanges / items / properties / socket / anyOf
      Removed value: -[
-  {
-    "type": "boolean"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / exchanges / items / properties / socket / type
      Added value: +[
+  "boolean",
+  "null"
+]
    • removedOutput schema / properties / exchanges / items / properties / tradingPairs / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / exchanges / items / properties / tradingPairs / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / exchanges / items / properties / volumeUsd / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / exchanges / items / properties / volumeUsd / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds useful behavioral context: results are ranked by 24-hour volume)Skip a listing, and a specific lookup returns details such as volume, trading pairs, and market share.

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 sentences with no filler. The action, scope, and optional parameter behavior are all front-loaded and immediately actionable.

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?

The tool is simple, the annotations already convey the non-destructive read-only nature, and an output schema exists. The description covers the two modes of operation well enough for an agent to decide whether to call it and what to pass.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds meaning by clarifying the two modes: omitting exchangeId returns a ranked list, while passing it returns details for that exchange. It also supplies valid value examples (binance, coinbase), going beyond the bare schema.

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 names a specific verb and resource (

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?

It explicitly explains the optional exchangeId behavior and what response mode it triggers, which is practical usage guidance. It does not name sibling alternatives or state exclusion cases, but the sibling set contains no other exchange-listing tool, so no stronger exclusion is needed.

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

All truss44-mcp-crypto-price toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources