Skip to main content
Glama
paperinvest

Paper MCP Server

by paperinvest

get_quote

Retrieve real-time stock quotes for a specified symbol using Paper MCP Server, enabling efficient access to market data for informed trading decisions.

Instructions

Get real-time quote for a symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol

Implementation Reference

  • The handler for the 'get_quote' tool. It makes an authenticated API request to retrieve real-time quote data for the specified stock symbol.
    case 'get_quote':
      response = await api.get(`/market-data/quote/${args.symbol}`);
      break;
  • Tool metadata including name, description, and input schema validation for the 'get_quote' tool.
      name: 'get_quote',
      description: 'Get real-time quote for a symbol',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string', description: 'Stock symbol' }
        },
        required: ['symbol']
      }
    },
  • src/index.ts:388-392 (registration)
    Registers the 'get_quote' tool (along with others) with the MCP server by including it in the tools list returned for ListTools requests.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
      return {
        tools
      };
    });
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'real-time' but does not specify data sources, latency, rate limits, authentication needs, or error handling. This leaves significant gaps in understanding the tool's operational behavior.

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 is front-loaded and appropriately sized for its purpose, making it highly concise and well-structured.

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 lack of annotations and output schema, the description is incomplete. It does not explain return values, error conditions, or behavioral traits like rate limits, which are crucial for a real-time data tool. This leaves the agent with insufficient context for effective use.

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 schema description coverage is 100%, with the parameter 'symbol' clearly documented as a 'Stock symbol'. The description adds no additional meaning beyond this, such as format examples or constraints, so it meets the baseline for adequate but unenhanced parameter documentation.

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 verb ('Get') and resource ('real-time quote for a symbol'), making the purpose specific and understandable. However, it does not distinguish this tool from its sibling 'get_batch_quotes', which handles multiple symbols, leaving room for improvement in sibling differentiation.

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_batch_otes' for multiple symbols or other market data tools. It lacks explicit instructions on context, prerequisites, or exclusions, offering minimal usage direction.

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