Skip to main content
Glama
paperinvest

Paper MCP Server

by paperinvest

get_day_trades

Retrieve day trade activity for a specific portfolio using portfolio ID, with options to paginate results for efficient data access through the Paper MCP Server.

Instructions

Get day trade activity for a portfolio

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoResults per page (default: 50)
pageNoPage number (default: 1)
portfolioIdYesPortfolio ID

Implementation Reference

  • Handler for the 'get_day_trades' tool. Makes an authenticated API call to retrieve day trade activities for the specified portfolio with optional pagination parameters.
    case 'get_day_trades':
      response = await api.get(`/accounts/portfolios/${args.portfolioId}/day-trades`, {
        params: {
          page: args.page || 1,
          limit: args.limit || 50
        }
      });
      break;
  • Tool definition including name, description, and input schema for 'get_day_trades'. Used for tool listing and validation.
    {
      name: 'get_day_trades',
      description: 'Get day trade activity for a portfolio',
      inputSchema: {
        type: 'object',
        properties: {
          portfolioId: { type: 'string', description: 'Portfolio ID' },
          page: { type: 'number', description: 'Page number (default: 1)' },
          limit: { type: 'number', description: 'Results per page (default: 50)' }
        },
        required: ['portfolioId']
      }
    },
  • src/index.ts:388-392 (registration)
    Registers the list tools handler which returns the array of all tools including 'get_day_trades'.
    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 states the action ('Get day trade activity') but does not disclose any behavioral traits such as whether this is a read-only operation, potential rate limits, authentication needs, or what the output format looks like. This is a significant gap for a tool with no annotation coverage.

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 unnecessary words. It is front-loaded and appropriately sized, 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 retrieving financial data, the lack of annotations, and no output schema, the description is incomplete. It does not cover behavioral aspects like safety, performance, or return values, leaving gaps that could hinder an agent's ability to use the 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 input schema has 100% description coverage, with clear documentation for 'portfolioId', 'limit', and 'page'. The description does not add any meaning beyond what the schema provides, such as explaining what 'day trade activity' entails or how parameters interact. Given the high schema coverage, a baseline score of 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 'Get day trade activity for a portfolio' clearly states the verb ('Get') and resource ('day trade activity for a portfolio'), making the purpose understandable. However, it does not distinguish this tool from sibling tools like 'get_portfolio_activities' or 'get_today_filled_orders', which might also involve activity retrieval, so it lacks explicit 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. There is no mention of context, prerequisites, or exclusions, such as how it differs from 'get_portfolio_activities' or 'get_today_filled_orders'. This leaves the agent without clear usage instructions.

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