Skip to main content
Glama
paperinvest

Paper MCP Server

by paperinvest

get_batch_quotes

Fetch real-time stock quotes for multiple symbols in a single request through the Paper MCP Server, enabling efficient market data retrieval for AI-driven trading and analysis.

Instructions

Get real-time quotes for multiple symbols

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolsYesArray of stock symbols

Implementation Reference

  • Handler implementation for get_batch_quotes tool. Makes a POST request to the Paper Invest API /market-data/quotes/batch endpoint with the array of symbols to retrieve real-time quotes for multiple symbols.
    case 'get_batch_quotes':
      response = await api.post('/market-data/quotes/batch', {
        symbols: args.symbols
      });
      break;
  • Schema definition for the get_batch_quotes tool, including name, description, and input schema requiring an array of stock symbols.
    {
      name: 'get_batch_quotes',
      description: 'Get real-time quotes for multiple symbols',
      inputSchema: {
        type: 'object',
        properties: {
          symbols: { 
            type: 'array',
            items: { type: 'string' },
            description: 'Array of stock symbols'
          }
        },
        required: ['symbols']
      }
    },
Behavior2/5

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

With no annotations provided, the description carries full burden but only states it gets 'real-time quotes' without disclosing behavioral traits. It doesn't mention whether this is a read-only operation, latency expectations, rate limits, authentication needs, or what happens with invalid symbols. For a financial data tool with zero annotation coverage, this is insufficient.

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 a single, efficient sentence that directly states the tool's function without unnecessary words. It's appropriately sized and front-loaded with the core purpose, making it easy to parse quickly.

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?

Given the complexity of financial data tools and the absence of both annotations and an output schema, the description is incomplete. It doesn't explain what the quotes include (e.g., price, volume, timestamp), how errors are handled, or the response format, leaving significant gaps for an AI agent to use this tool effectively.

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?

The description adds minimal value beyond the input schema, which has 100% coverage and clearly documents the 'symbols' parameter as an array of stock symbols. The description implies 'multiple symbols' aligns with the array parameter but doesn't provide additional context like symbol format examples, maximum array size, or handling of mixed valid/invalid symbols.

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 clearly states the action ('Get real-time quotes') and resource ('for multiple symbols'), making the purpose immediately understandable. It distinguishes from the sibling 'get_quote' by specifying 'multiple symbols' rather than a single symbol. However, it doesn't specify the data source or format of the quotes, which keeps it from being a perfect 5.

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_quote' for single symbols or other market data tools. It doesn't mention prerequisites, rate limits, or any contextual constraints for batch operations versus individual queries.

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

Related 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/paperinvest/mcp-server'

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