Skip to main content
Glama
paperinvest

Paper MCP Server

by paperinvest

is_market_open

Determine if the market is open for a specific stock symbol using the Paper MCP Server. Ideal for traders and AI assistants to verify market status and make informed decisions.

Instructions

Check if market is open for a symbol

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesStock symbol

Implementation Reference

  • Handler implementation for the 'is_market_open' tool. It extracts the symbol from arguments and calls the backend API endpoint `/market-data/is-market-open/${symbol}` to get the market open status.
    case 'is_market_open':
      response = await api.get(`/market-data/is-market-open/${args.symbol}`);
      break;
  • Input schema for the 'is_market_open' tool, specifying that a 'symbol' string parameter is required.
    inputSchema: {
      type: 'object',
      properties: {
        symbol: { type: 'string', description: 'Stock symbol' }
      },
      required: ['symbol']
    }
  • src/index.ts:331-341 (registration)
    Tool registration entry in the tools array, defining the name, description, and input schema for listing via ListToolsRequest.
    {
      name: 'is_market_open',
      description: 'Check if market is open for a symbol',
      inputSchema: {
        type: 'object',
        properties: {
          symbol: { type: 'string', description: 'Stock symbol' }
        },
        required: ['symbol']
      }
    },
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 states the tool checks market status but doesn't mention whether this requires authentication, has rate limits, returns real-time or cached data, or handles errors. For a tool with zero annotation coverage, this leaves significant gaps in understanding its 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 purpose without any wasted words. It is appropriately sized and front-loaded, 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 lack of annotations and output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., boolean, status details, error handling) or behavioral aspects like authentication needs. For a tool in a financial context with sibling tools providing related data, more context is needed to ensure proper 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' documented as 'Stock symbol'. The description adds no additional meaning beyond this, such as format examples (e.g., 'AAPL') or constraints. With high schema coverage, the baseline score of 3 is appropriate as the schema does the heavy lifting.

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 ('Check') and resource ('market is open for a symbol'), making the purpose immediately understandable. However, it doesn't distinguish this tool from sibling tools like 'get_market_hours', which might provide overlapping functionality for determining market status.

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 guidance is provided on when to use this tool versus alternatives like 'get_market_hours' or 'get_quote' (which might include market status). The description lacks context about prerequisites, timing, or exclusions, leaving the agent to infer usage scenarios.

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