Skip to main content
Glama

vybsly_stocks

Fetch live stock prices for one or more ticker symbols. Automatically saves data to a historical almanac for trend lookups.

Instructions

Live stock prices for one or more ticker symbols. Auto-saves to historical almanac for trend lookups.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolsYesComma-separated tickers, e.g. AAPL,TSLA,NVDA

Implementation Reference

  • index.js:93-103 (registration)
    Tool registration entry in the TOOLS array, defining the tool name, description, and input schema (required 'symbols' string).
    {
      name: 'vybsly_stocks',
      description: 'Live stock prices for one or more ticker symbols. Auto-saves to historical almanac for trend lookups.',
      inputSchema: {
        type: 'object',
        properties: {
          symbols: { type: 'string', description: 'Comma-separated tickers, e.g. AAPL,TSLA,NVDA' }
        },
        required: ['symbols']
      }
    },
  • Input schema for vybsly_stocks: expects an object with a required 'symbols' string (comma-separated tickers).
      inputSchema: {
        type: 'object',
        properties: {
          symbols: { type: 'string', description: 'Comma-separated tickers, e.g. AAPL,TSLA,NVDA' }
        },
        required: ['symbols']
      }
    },
  • Handler implementation: calls the Vybsly API at /stocks endpoint with the provided symbols parameter.
    case 'vybsly_stocks':
      result = await vybslyCall('/stocks', { symbols: args.symbols });
      break;
  • Generic helper function used by vybsly_stocks to make HTTP GET requests to the Vybsly API with query params, API key authentication, and error handling.
    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();
    }
  • The 'market-snapshot' prompt template that uses vybsly_stocks as part of its orchestration steps.
    case 'market-snapshot':
      return {
        description: `Market snapshot: ${args.symbols}`,
        messages: [{
          role: 'user',
          content: {
            type: 'text',
            text: `Build a market snapshot for: ${args.symbols}\n\nSteps:\n1. vybsly_stocks symbols="${args.symbols}".\n2. For each ticker, vybsly_news query="<ticker> stock", hours=24, limit=3.\n\nProduce, for each ticker:\n- **TICKER**: $price (▲/▼ X.XX%)\n- One-line headline summary of today's top story.\n- 2-3 bullets of key drivers.\n\nEnd with a ~2 sentence "What to watch" section covering the portfolio as a whole.`
          }
        }]
Behavior4/5

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

The description discloses an important behavioral trait—automatic saving to a historical almanac for trend lookups—beyond the absent annotations. This adds transparency, though it does not mention rate limits, authentication, or other potential side effects.

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?

The description is exceptionally concise with two sentences that contain no filler. Every part adds value: the core functionality and a notable side effect (auto-saving).

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?

Given the tool's simplicity (one parameter, no output schema), the description is fully adequate. It covers the essential purpose and a key behavioral aspect, leaving no critical gaps for an AI agent to use it correctly.

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?

Input schema coverage is 100% with a clear description of the 'symbols' parameter as comma-separated tickers. The tool description adds no additional parameter semantics beyond what the schema already provides, meeting the baseline for a well-documented 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 clearly states it provides live stock prices for one or more ticker symbols, with a specific verb 'get live stock prices' and resource 'tickers'. This distinguishes it from sibling tools like vybsly_crypto or vybsly_news, which cover different domains.

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?

While the description implies usage for stock price retrieval, it offers no explicit guidance on when to use this tool versus alternatives or exclusions. The context is clear from the name, but no when-not-to-use or alternative references are provided.

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