Skip to main content
Glama
paperinvest

Paper MCP Server

by paperinvest

get_portfolio_activities

Retrieve activity logs for a specific portfolio, enabling users to track actions and filter results by category, page, or limit for detailed insights.

Instructions

Get activity log for a portfolio

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
categoryNoFilter by category (optional)
limitNoResults per page (default: 20)
pageNoPage number (default: 1)
portfolioIdYesPortfolio ID

Implementation Reference

  • Handler implementation for the 'get_portfolio_activities' tool. Constructs query parameters for pagination and optional category filter, then fetches activity log via API call to `/activity-log/portfolio/{portfolioId}`.
    case 'get_portfolio_activities':
      const params: any = {
        page: args.page || 1,
        limit: args.limit || 20
      };
      if (args.category) {
        params.category = args.category;
      }
      response = await api.get(`/activity-log/portfolio/${args.portfolioId}`, { params });
      break;
  • src/index.ts:345-357 (registration)
    Tool registration in the tools array, including name, description, and input schema definition for validation.
      name: 'get_portfolio_activities',
      description: 'Get activity log 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: 20)' },
          category: { type: 'string', description: 'Filter by category (optional)' }
        },
        required: ['portfolioId']
      }
    },
  • Input schema for the 'get_portfolio_activities' tool, defining parameters and validation rules.
    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: 20)' },
        category: { type: 'string', description: 'Filter by category (optional)' }
      },
      required: ['portfolioId']
    }
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 activity log' which implies a read-only operation, but does not disclose any behavioral traits like pagination details, rate limits, authentication needs, or what an 'activity log' entails. This leaves significant gaps for a tool with 4 parameters and no output schema.

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 understand at a glance.

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 (4 parameters, no annotations, no output schema), the description is incomplete. It does not explain the return values, behavioral aspects like pagination or filtering, or how it differs from sibling tools. This leaves the agent with insufficient context to use the tool effectively beyond basic parameter input.

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%, so the schema fully documents all parameters. The description does not add any meaning beyond the schema, such as explaining what 'category' filters or the structure of the activity log. With high schema coverage, the baseline is 3, as the description does not compensate but also does not detract.

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 ('activity log for a portfolio'), making the purpose evident. However, it does not differentiate from sibling tools like 'get_account' or 'get_portfolio', which also retrieve portfolio-related data, so it lacks sibling distinction for a perfect score.

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. It does not mention any context, exclusions, or prerequisites, such as when to prefer this over other portfolio-related tools like 'get_portfolio_equities' or 'get_portfolio_options'.

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