Skip to main content
Glama

vybsly_crypto

Get live cryptocurrency prices and market data for any ticker symbol such as BTC, ETH, or SOL.

Instructions

Live cryptocurrency prices and market data.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesCrypto ticker, e.g. BTC, ETH, SOL

Implementation Reference

  • The case handler for 'vybsly_crypto' tool. Calls vybslyCall('/crypto', { symbol: args.symbol }) to fetch crypto market data.
    case 'vybsly_crypto':
      result = await vybslyCall('/crypto', { symbol: args.symbol });
      break;
  • The tool definition/schema for 'vybsly_crypto' with name, description, and inputSchema requiring a 'symbol' string.
    {
      name: 'vybsly_crypto',
      description: 'Live cryptocurrency prices and market data.',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string', description: 'Crypto ticker, e.g. BTC, ETH, SOL' }
        },
        required: ['symbol']
      }
  • index.js:417-417 (registration)
    The tool is registered via ListToolsRequestSchema handler which returns the TOOLS array containing 'vybsly_crypto'.
    server.setRequestHandler(ListToolsRequestSchema, async () => ({ tools: TOOLS }));
  • The vybslyCall helper function used by the handler to make HTTP requests to the Vybsly API at /crypto endpoint.
    async function vybslyCall(path, params = {}) {
      const qs = new URLSearchParams(params).toString();
      const url = `${VYBSLY_BASE}${path}${qs ? '?' + qs : ''}`;
      const headers = { 'Accept': 'application/json' };
      if (API_KEY) headers['X-API-Key'] = API_KEY;
      const res = await fetch(url, { headers });
      if (!res.ok) {
        const text = await res.text();
        throw new Error(`Vybsly API ${res.status}: ${text.slice(0, 300)}`);
      }
      return res.json();
    }
Behavior2/5

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

No annotations are provided, so the description bears full responsibility. It only states 'Live... market data' but does not disclose whether data is read-only, rate limits, or response format. This is insufficient for a tool with zero annotation support.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It could include more useful detail without becoming verbose.

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?

With no output schema and minimal description, the tool lacks information on what exactly is returned (e.g., price, market cap, volume). The description feels incomplete for a data retrieval tool.

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 a clear description of the 'symbol' parameter. The tool description adds no new meaning beyond what the schema already provides (same examples). 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?

The description 'Live cryptocurrency prices and market data' clearly identifies the resource (cryptocurrency) and action (retrieving prices/data). It distinguishes from siblings like vybsly_stocks by resource type, though it could be more specific.

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 explicit guidance on when to use this tool vs alternatives. The context of sibling tools (e.g., vybsly_stocks) implies differentiation by asset class, but the description does not state this.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/BlueFusionLab/vybsly-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server