Skip to main content
Glama
Sign In
e-arveldaja MCP Server

e-arveldaja MCP Server

by iseppo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Lightyear Portfolio Summary

lightyear_portfolio_summary
Read-onlyIdempotent

Estimate current Lightyear holdings and weighted-average cost from an account statement; use the analytical summary for portfolio insight, not to verify or adjust the FIFO ledger.

Instructions

Analytical weighted-average-cost (WAC) estimate of current Lightyear holdings from an account statement. Bookings use Lightyear's FIFO cost basis, so this differs from the registered investment-account balance after any sell; never use it to verify or adjust the FIFO ledger (use compute_account_balance on the investment account for the booked balance).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "lightyear_portfolio_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
file_refNoOpaque Lightyear AccountStatement file reference.
file_pathNoAccountStatement path/base64 input. Provide exactly one of file_path or file_ref.

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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious behavioral context: the result is an analytical estimate, not an authoritative balance, and it will diverge from the FIFO-booked account balance after any sell. It stops short of describing what the summary actually returns or how it handles unparseable statements.

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 sentences with essentially zero waste: the first defines the computation, the second carries the divergence warning and the alternative in a single clause. The most important disambiguation (estimate vs. booked balance) is front-loaded.

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?

With no output schema, the description carries the burden of telling the agent what comes back, and it never states the shape or contents of the 'summary' (holdings, WAC, quantities, currency). The safety and usage picture is complete, but return-value expectation for a zero-required-param analytical tool is left unstated.

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% and both parameters (file_ref, file_path) are documented in the schema, including the exactly-one-of constraint. The description adds no parameter-level detail beyond the phrase 'from an account statement', so baseline 3 applies.

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 resource and computation: a weighted-average-cost (WAC) estimate of current Lightyear holdings derived from an account statement. It distinguishes itself from the key sibling compute_account_balance, though it does not differentiate from other Lightyear-family tools such as parse_lightyear_statement or book_lightyear_trades.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit prohibition ('never use it to verify or adjust the FIFO ledger') and names the correct alternative for the booked balance (compute_account_balance on the investment account). The positive use case is implied directly by the stated purpose, so an agent has both the when and the when-not.

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