Skip to main content
Glama
paperinvest

Paper MCP Server

by paperinvest

get_account_orders

Retrieve order details for a specific account on Paper's trading platform. Specify account ID, page number, and results limit to fetch tailored data for analysis or management.

Instructions

Get orders for an account

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountIdYesAccount ID
limitNoResults per page (default: 10)
pageNoPage number (default: 1)

Implementation Reference

  • Handler implementation for the 'get_account_orders' tool. Makes an authenticated API GET request to fetch orders for the specified account ID with optional pagination parameters.
    case 'get_account_orders':
      response = await api.get(`/orders/account/${args.accountId}`, {
        params: { 
          page: args.page || 1, 
          limit: args.limit || 10 
        }
      });
      break;
  • src/index.ts:258-270 (registration)
    Tool registration object defining name, description, and input schema for 'get_account_orders'. This object is included in the tools list returned by ListToolsRequest handler.
    {
      name: 'get_account_orders',
      description: 'Get orders for an account',
      inputSchema: {
        type: 'object',
        properties: {
          accountId: { type: 'string', description: 'Account ID' },
          page: { type: 'number', description: 'Page number (default: 1)' },
          limit: { type: 'number', description: 'Results per page (default: 10)' }
        },
        required: ['accountId']
      }
    },
  • Input schema validation for the 'get_account_orders' tool parameters.
    inputSchema: {
      type: 'object',
      properties: {
        accountId: { type: 'string', description: 'Account ID' },
        page: { type: 'number', description: 'Page number (default: 1)' },
        limit: { type: 'number', description: 'Results per page (default: 10)' }
      },
      required: ['accountId']
    }
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 'Get orders' but does not clarify if this retrieves all orders, open orders, or includes pagination details (implied by parameters). It lacks information on permissions, rate limits, or response format, leaving significant gaps for a read operation.

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 with no wasted words. It is front-loaded and directly states the tool's function, 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?

For a tool with 3 parameters, no annotations, and no output schema, the description is incomplete. It does not explain what 'orders' entails (e.g., status, time range) or the return structure, leaving the agent to guess based on context or sibling tools, which is inadequate for reliable 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 input schema has 100% description coverage, documenting 'accountId', 'limit', and 'page' with defaults. The description adds no additional parameter semantics beyond what the schema provides, so it meets the baseline for high schema coverage without compensating value.

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 orders for an account' clearly states the verb 'Get' and resource 'orders for an account', making the purpose understandable. However, it lacks specificity to distinguish it from sibling tools like 'get_order' (singular) or 'get_today_filled_orders', which could cause confusion in tool selection.

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. With siblings like 'get_order' (for a specific order) and 'get_today_filled_orders' (for today's filled orders), the agent must infer usage from the name alone, which is insufficient for reliable tool selection.

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