Skip to main content
Glama
Sign In
Paper MCP Server

Paper MCP Server

by paperinvest
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_portfolio

Retrieve detailed portfolio information by specifying a portfolio ID, enabling users to manage and analyze trading data through the Paper MCP Server interface.

Instructions

Get portfolio details

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "portfolioId": "<portfolioId>"
    },
    "name": "get_portfolio"
  }
}

Input Schema

NameRequiredDescriptionDefault
portfolioIdYesPortfolio ID

Implementation Reference

  • src/index.ts:121-131 (schema)
    Tool definition including name, description, and input schema for validating portfolioId parameter.
    {
  name: 'get_portfolio',
  description: 'Get portfolio details',
  inputSchema: {
    type: 'object',
    properties: {
      portfolioId: { type: 'string', description: 'Portfolio ID' }
    },
    required: ['portfolioId']
  }
},
  • src/index.ts:426-428 (handler)
    Core handler logic: performs authenticated GET request to the Paper Invest API endpoint for portfolio details using the provided portfolioId.
    case 'get_portfolio':
  response = await api.get(`/accounts/portfolios/${args.portfolioId}`);
  break;
  • src/index.ts:388-392 (registration)
    Registers the listTools handler which exposes the get_portfolio tool (among others) to MCP clients.
    server.setRequestHandler(ListToolsRequestSchema, async () => {
  return {
    tools
  };
});

Schema Changelog

Changes observed during successful MCP inspections.

  1. Removedv1.0.0
  2. First observed

TDQS

C2.6/5.0
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 'Get portfolio details' without disclosing behavioral traits such as read-only vs. mutative nature, error conditions, or response format. It implies a read operation but lacks confirmation or details like rate limits or permissions needed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise with 'Get portfolio details', which is front-loaded and wastes no words. However, it's arguably too brief, bordering on under-specified, but within the bounds of efficient communication for a simple tool.

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 no annotations, no output schema, and a simple input schema, the description is incomplete. It doesn't explain what 'details' includes, how to interpret results, or any behavioral context, making it inadequate for a tool that likely returns complex portfolio data among many siblings.

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?

Schema description coverage is 100%, with the parameter 'portfolioId' documented in the schema. The description adds no meaning beyond the schema, as it doesn't explain what a portfolio ID is or provide context. Baseline 3 is appropriate since the schema handles parameter documentation adequately.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Get portfolio details' clearly states the action (get) and resource (portfolio), but it's vague about what 'details' includes compared to siblings like get_portfolio_equities or get_portfolio_activities. It distinguishes minimally by not specifying scope, but lacks the specificity needed for a 4 or 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?

No guidance is provided on when to use this tool versus alternatives like get_account_portfolios or other portfolio-specific tools. The description offers no context about prerequisites, timing, or exclusions, leaving usage entirely implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools

Related Tools