Skip to main content
Glama
Sign In

vek-data

by io.github.Ratiborro
OverviewDiscussionsAdmin

coin_price

Current coin market prices via CoinGecko simple price.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "coin_price"
  }
}

Input Schema

NameRequiredDescriptionDefault
vsNoquote currency, default usd
idsNocomma-separated coin ids, e.g. bitcoin,ethereum

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

No annotations exist, so the description carries the full behavioral burden. It discloses the data source ('CoinGecko simple price'), which is useful, but says nothing about rate limits, API key/auth requirements, caching/freshness of 'current' prices, or failure behavior for unknown coin ids.

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 sentence with zero waste, front-loading the resource ('Current coin market prices') before the implementation note. Every word earns its place.

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

Completeness2/5

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

There is no output schema, so the description should explain what is returned (a per-coin, per-quote-currency price map) and how missing ids are handled. It also omits the fact that both parameters are optional and what the defaults produce. For a tool with no annotations or output schema, this leaves real 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 description coverage is 100%, so both parameters ('vs' and 'ids') are already documented in the schema, making 3 the baseline. The description adds no format detail beyond the schema, only the upstream source, so it neither compensates nor detracts.

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 specific verb+resource: 'Current coin market prices'. This is clearly distinct from siblings crypto_news, get_balance, and get_block, so an agent can route to it without opening the schema. It doesn't explicitly name what it is not, but the resource is unambiguous.

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?

No when-to-use guidance, no exclusions, and no mention of alternatives. 'Current' hints that this is a spot-price lookup versus historical data, but the agent must infer that. Nothing tells it when this tool is the right choice over the siblings.

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

All vek-data 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