Skip to main content
Glama
iseppo

e-arveldaja MCP Server

by iseppo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Parse Lightyear Account Statement

parse_lightyear_statement
Read-onlyIdempotent

Parse a Lightyear account statement CSV to summarize trades and distributions, or include individual rows for detailed review. Filter entries by date range and file reference or path.

Instructions

Parse a Lightyear account statement CSV. Returns summary by default; set include_rows=true for trade/distribution details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
date_toNoOnly include entries up to this date (YYYY-MM-DD)
file_refNoOpaque Lightyear AccountStatement file reference.
date_fromNoOnly include entries from this date (YYYY-MM-DD)
file_pathNoAccountStatement path/base64 input. Provide exactly one of file_path or file_ref.
include_rowsNoInclude individual trade/distribution rows (default false — summary only)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.29.2
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed3 schema fields changedv0.25.2
    • changedInput schema / properties / file_path / description
      Previous value: -"Absolute path to Lightyear AccountStatement CSV file."New value: +"AccountStatement path/base64 input. Provide exactly one of file_path or file_ref."
    • addedInput schema / properties / file_ref
      Added value: +{
+  "description": "Opaque Lightyear AccountStatement file reference.",
+  "type": "string"
+}
    • removedInput schema / required
      Removed value: -[
-  "file_path"
-]
  3. First observedv0.18.1

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare the safe read-only, idempotent, non-destructive profile. The description adds that it returns a summary by default and detailed rows when include_rows=true, but it does not explain error behavior, file-handling constraints, or output detail beyond the 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?

Two tightly written sentences with zero waste. The core action is front-loaded, and the default versus detailed-return behavior follows immediately.

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

Completeness4/5

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

For a read-only CSV parser with a rich input schema and no output schema, the description gives enough for an agent to invoke it correctly. It could say more about what the summary contains, but the essential selection and invocation information is present.

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%, so the schema fully documents all five parameters. The description only restates the include_rows behavior and adds no syntax or format detail beyond what the schema already provides.

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 names a specific verb and resource: parsing a Lightyear account statement CSV. It distinguishes the tool from generic parsers and from siblings like parse_lightyear_capital_gains by the 'account statement' resource, though it does not explicitly name alternatives.

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?

It does not state when to use this tool versus alternatives such as parse_lightyear_capital_gains, book_lightyear_trades, or lightyear_portfolio_summary. The include_rows sentence is parameter guidance, not selection guidance.

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