Skip to main content
Glama

truss44-mcp-crypto-price

by ai.smithery
OverviewDiscussionsAdmin

Get Crypto Price

price-get
Read-onlyIdempotent

Get real-time price, 24-hour change percentage, trading volume, and market cap for any cryptocurrency by symbol or name.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesCryptocurrency symbol or name (e.g. BTC or Bitcoin)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
rankYes
symbolYes
priceUsdYes
marketCapUsdYes
volumeUsd24HrYes
changePercent24HrYes

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 / changePercent24Hr / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / changePercent24Hr / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / marketCapUsd / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / marketCapUsd / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / rank / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / rank / type
      Added value: +[
+  "string",
+  "null"
+]
    • removedOutput schema / properties / volumeUsd24Hr / anyOf
      Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]
    • addedOutput schema / properties / volumeUsd24Hr / type
      Added value: +[
+  "string",
+  "null"
+]
  2. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered. The description contributes the 'real-time' freshness qualifier and the exact metrics returned, but it does not address behavior for unknown symbols or rate limiting. It does not contradict the annotations.

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?

A single 17-word sentence that front-loads the verb and resource, then lists the returned metrics without filler. Every word earns its place.

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?

For a one-parameter, read-only tool with a full output schema and safety annotations, the description covers everything needed to select and invoke it correctly: what it returns, the input flexibility, and the scope. No critical information is missing.

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?

Schema coverage is 100%: the single 'symbol' parameter includes type, minLength, and an example (BTC or Bitcoin). The description's phrase 'by symbol or name' merely restates what the schema already documents, adding no new meaning. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a clear verb ('Get') and a specific resource: real-time price, 24-hour change percentage, trading volume, and market cap, for any cryptocurrency by symbol or name. The resource list makes it unambiguous and distinct in content from siblings like price-convert or market-rates, though it does not explicitly name alternatives.

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

Usage Guidelines3/5

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

Intended usage is inferable from 'real-time' and the listed metrics, implying 'use when you need a current price snapshot.' However, there is no explicit guidance on when to choose this tool over siblings like assets-info, market-rates, or analysis-historical, and no exclusions are stated.

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