Skip to main content
Glama
alpacahq

alpaca-mcp-server

Official
by alpacahq

get_account_activities

Retrieve account activities like fills, dividends, and transfers with filters for date, category, order, and activity type to track trading history.

Instructions

Returns a list of account activities such as fills, dividends, and transfers.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoFilter activities by their creation date (created_at), not the activity's settlement date. For non-trade activities such as fees, the creation date is typically the day after the trade date (in UTC). Both formats YYYY-MM-DD and YYYY-MM-DDTHH:MM:SSZ are supported.
afterNoGet activities created after this date. Both formats YYYY-MM-DD and YYYY-MM-DDTHH:MM:SSZ are supported.
untilNoGet activities created before this date. Both formats YYYY-MM-DD and YYYY-MM-DDTHH:MM:SSZ are supported.
categoryNoThe activity category. Cannot be used with "activity_types" parameter.
order_idNoFilter activities associated with a specific order. Useful for retrieving the fills that make up a completely filled order.
directionNoThe chronological order of response based on the activity datetime.desc
page_sizeNoThe maximum number of entries to return in the response.
page_tokenNoToken used for pagination. Provide the ID of the last activity from the last page to retrieve the next set of results.
activity_typesNoA comma-separated list of activity types used to filter the results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv2.3.2
    • changedInput schema / properties / activity_types / items / description
      Previous value: -"- FILL\n  Order fills (both partial and full fills)\n\n- TRANS\n  Cash transactions (both CSD and CSW)\n\n- MISC\n  Miscellaneous or rarely used activity types (All types except those in TRANS, DIV, or FILL)\n\n- ACATC\n  ACATS IN/OUT (Cash)\n\n- ACATS\n  ACATS IN/OUT (Securities)\n\n- CFEE\n  Crypto fee\n\n- CSD\n  Cash deposit(+)\n\n- CSW\n  Cash withdrawal(-)\n\n- DIV\n  Dividends\n\n- DIVCGL\n  Dividend (capital gain long term)\n\n- DIVCGS\n  Dividend (capital gain short term)\n\n- DIVFEE\n  Dividend fee\n\n- DIVFT\n  Dividend adjusted (Foreign Tax Withheld)\n\n- DIVNRA\n  Dividend adjusted (NRA Withheld)\n\n- DIVROC\n  Dividend return of capital\n\n- DIVTW\n  Dividend adjusted (Tefra Withheld)\n\n- DIVTXEX\n  Dividend (tax exempt)\n\n- FEE\n  Fee denominated in USD\n\n- INT\n  Interest (credit/margin)\n\n- INTNRA\n  Interest adjusted (NRA Withheld)\n\n- INTTW\n  Interest adjusted (Tefra Withheld)\n\n- JNL\n  Journal entry\n\n- JNLC\n  Journal entry (cash)\n\n- JNLS\n  Journal entry (stock)\n\n- MA\n  Merger/Acquisition\n\n- NC\n  Name change\n\n- OPASN\n  Option assignment\n\n- OPCA\n  Option corporate action\n\n- OPCSH\n  Option cash deliverable for non-standard contracts\n\n- OPEXC\n  Option exercise\n\n- OPEXP\n  Option expiration\n\n- OPTRD\n  Option trade\n\n- PTC\n  Pass Thru Charge\n\n- PTR\n  Pass Thru Rebate\n\n- REORG\n  Reorg CA\n\n- SPIN\n  Stock spinoff\n\n- SPLIT\n  Stock split\n\n- FOPT\n  Free of Payment Transfers"New value: +"- FILL\n  Order fills (both partial and full fills)\n\n- TRANS\n  Cash transactions (both CSD and CSW)\n\n- MISC\n  Miscellaneous or rarely used activity types (All types except those in TRANS, DIV, or FILL)\n\n- ACATC\n  ACATS IN/OUT (Cash)\n\n- ACATS\n  ACATS IN/OUT (Securities)\n\n- CFEE\n  Crypto fee\n\n- CGD\n  Capital gain distribution\n\n- CSD\n  Cash deposit(+)\n\n- CSW\n  Cash withdrawal(-)\n\n- DIV\n  Dividends\n\n- DIVCGL\n  Dividend (capital gain long term)\n\n- DIVCGS\n  Dividend (capital gain short term)\n\n- DIVFEE\n  Dividend fee\n\n- DIVFT\n  Dividend adjusted (Foreign Tax Withheld)\n\n- DIVNRA\n  Dividend adjusted (NRA Withheld)\n\n- DIVROC\n  Dividend return of capital\n\n- DIVTW\n  Dividend adjusted (Tefra Withheld)\n\n- DIVTXEX\n  Dividend (tax exempt)\n\n- FEE\n  Fee denominated in USD\n\n- INT\n  Interest (credit/margin)\n\n- INTNRA\n  Interest adjusted (NRA Withheld)\n\n- INTTW\n  Interest adjusted (Tefra Withheld)\n\n- JNL\n  Journal entry\n\n- JNLC\n  Journal entry (cash)\n\n- JNLS\n  Journal entry (stock)\n\n- MA\n  Merger/Acquisition\n\n- NC\n  Name change\n\n- OPASN\n  Option assignment\n\n- OPCA\n  Option corporate action\n\n- OPCSH\n  Option cash deliverable for non-standard contracts\n\n- OPEXC\n  Option exercise\n\n- OPEXP\n  Option expiration\n\n- OPTRD\n  Option trade\n\n- PTC\n  Pass Thru Charge\n\n- PTR\n  Pass Thru Rebate\n\n- REO\n  Reorganization\n\n- REORG\n  Reorg CA\n\n- SPIN\n  Stock spinoff\n\n- SPLIT\n  Stock split\n\n- FOPT\n  Free of Payment Transfers\n\n- OCT\n  On chain transactions (blockchain deposits/withdrawals)"
    • changedInput schema / properties / activity_types / items / enum
      Previous value: -[
      -  "FILL",
      -  "TRANS",
      -  "MISC",
      -  "ACATC",
      -  "ACATS",
      -  "CFEE",
      -  "CSD",
      -  "CSW",
      -  "DIV",
      -  "DIVCGL",
      -  "DIVCGS",
      -  "DIVFEE",
      -  "DIVFT",
      -  "DIVNRA",
      -  "DIVROC",
      -  "DIVTW",
      -  "DIVTXEX",
      -  "FEE",
      -  "INT",
      -  "INTNRA",
      -  "INTTW",
      -  "JNL",
      -  "JNLC",
      -  "JNLS",
      -  "MA",
      -  "NC",
      -  "OPASN",
      -  "OPCA",
      -  "OPCSH",
      -  "OPEXC",
      -  "OPEXP",
      -  "OPTRD",
      -  "PTC",
      -  "PTR",
      -  "REORG",
      -  "SPIN",
      -  "SPLIT",
      -  "FOPT"
      -]New value: +[
      +  "FILL",
      +  "TRANS",
      +  "MISC",
      +  "ACATC",
      +  "ACATS",
      +  "CFEE",
      +  "CGD",
      +  "CSD",
      +  "CSW",
      +  "DIV",
      +  "DIVCGL",
      +  "DIVCGS",
      +  "DIVFEE",
      +  "DIVFT",
      +  "DIVNRA",
      +  "DIVROC",
      +  "DIVTW",
      +  "DIVTXEX",
      +  "FEE",
      +  "INT",
      +  "INTNRA",
      +  "INTTW",
      +  "JNL",
      +  "JNLC",
      +  "JNLS",
      +  "MA",
      +  "NC",
      +  "OPASN",
      +  "OPCA",
      +  "OPCSH",
      +  "OPEXC",
      +  "OPEXP",
      +  "OPTRD",
      +  "PTC",
      +  "PTR",
      +  "REO",
      +  "REORG",
      +  "SPIN",
      +  "SPLIT",
      +  "FOPT",
      +  "OCT"
      +]
    • addedInput schema / properties / activity_types / items / examples
      Added value: +[
      +  "FILL"
      +]
    • removedInput schema / properties / activity_types / items / x-examples
      Removed value: -{
      -  "example-1": "FILL"
      -}
    • changedInput schema / properties / date / description
      Previous value: -"Filter activities by the activity date. Both formats YYYY-MM-DD and YYYY-MM-DDTHH:MM:SSZ are supported."New value: +"Filter activities by their creation date (created_at), not the activity's settlement date. For non-trade activities such as fees, the creation date is typically the day after the trade date (in UTC). Both formats YYYY-MM-DD and YYYY-MM-DDTHH:MM:SSZ are supported."
    • addedInput schema / properties / order_id
      Added value: +{
      +  "description": "Filter activities associated with a specific order. Useful for retrieving the fills that make up a completely filled order.",
      +  "example": "fe060a1b-5b45-4eba-ba46-c3a3345d8255",
      +  "format": "uuid",
      +  "type": "string"
      +}
  2. Addedv2.0.0

TDQS

B3.1/5.0
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 behavioral disclosure burden. It only says returns a list; there is no mention of pagination, default ordering, date semantics (created_at vs settlement date), or how filtering parameters affect the result. The schema partially covers some of this, but the description itself adds little behavioral context.

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?

A single, front-loaded sentence with no filler. The examples are meaningful and help convey the tool's scope without adding unnecessary detail.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema and 100% parameter coverage reduce the burden on the description. However, with nine parameters and a large sibling set, the description lacks usage context such as when to choose this over get_account_activities_by_type or how pagination behaves. It is adequate but leaves clear gaps.

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?

Input schema coverage is 100%, so the baseline is 3. The description's examples of fills, dividends, and transfers loosely align with activity_types but add no parameter semantics or syntax beyond what the schema already documents. It does not compensate with additional meaning.

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?

States a specific verb and resource: returns account activities, with informative examples (fills, dividends, transfers). It is clear but does not explicitly distinguish itself from the sibling get_account_activities_by_type, though the difference is partially inferable from the name.

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 on when to use this tool versus alternatives such as get_account_activities_by_type or get_orders. It does not state scenarios, exclusions, or that a more targeted tool exists for filtered activity types.

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