Skip to main content
Glama
Sign In
claw-mcp-toolkit

claw-mcp-toolkit

by ElromEvedElElyon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

crypto_price

Get current cryptocurrency prices, market capitalization, and 24-hour change data for any coin. Input a coin ID to retrieve real-time financial metrics.

Instructions

Get current price, market cap, and 24h change for any cryptocurrency

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "coin": "<coin>"
    },
    "name": "crypto_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
coinYesCoin ID (e.g. bitcoin, ethereum, solana)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It partially compensates by disclosing the return data structure (price, market cap, 24h change), but omits critical behavioral details like data freshness, rate limits, or authentication requirements.

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?

Single sentence that efficiently packs the tool's purpose, scope, and return value information without redundancy. Every word earns its place.

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?

Lacking annotations and output schema, the description partially compensates by specifying the three data points returned. However, for financial data, omitting information about real-time vs cached data or data sources leaves meaningful gaps.

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% with the 'coin' parameter well-documented in the schema itself. The description implies the parameter usage ('for any cryptocurrency') but adds minimal semantic detail beyond the schema, meeting the baseline for high-coverage schemas.

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?

Clearly states the specific data retrieved (current price, market cap, 24h change) and the target resource (any cryptocurrency). The specificity of 'current' and the three metrics distinguishes it implicitly from siblings like crypto_price_history and crypto_market_overview, though it does not explicitly name them.

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?

Provides no guidance on when to use this tool versus alternatives such as crypto_price_history or stbtcx_price, nor does it mention prerequisites like valid coin IDs or rate limits.

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

Deploy Server

Other Tools