Skip to main content
Glama

Fortunest demo

Tax lots

tax_lots
Read-onlyIdempotent

DEMO portfolio (synthetic, shared, read-only). Read one slice of the illustrative tax-lot orientation (the Taxes tab) instead of the whole context. view is required: 'maturities' = the open lots whose time test is coming up, soonest first (date; daysToExempt = days left until that date, the Taxes tab's 'N days to go'; symbol, qty, valueEur); 'openLots' = the per-asset lot lines, largest position first (openQty, taxFreeQty, taxFreeValueEur, nextMaturity, warnings); 'annual' = the realized-gains table per year, newest year first (proceedsEur = gross, feesEur = broker fees deducted, timeExemptGainEur, capTaxableGainEur = the part of time-test gains the exempt-proceeds cap taxed, netTaxableGainEur, estimatedTaxEur); 'ytd' = this year's proceeds against the limit, the exempt-proceeds cap (exemptGainsCap: time-test-exempt proceeds, scope 'crypto' from 2026), what is already sellable tax-free and the next maturity. symbol (one ticker) or symbols (several, in one call) filter maturities and openLots; year filters annual; limit is 1-50 (default 10) with offset/nextOffset. Every answer carries activeRules. Approximate orientation only — not tax advice and never input for a tax report. Each '…Eur' field now also ships under its currency-neutral name (amountEur→amount, buyEur→buy, valueEur→value, totalEur→totalAmount); the '…Eur' twins are DEPRECATED and will be removed — read the neutral name.

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": {
      "view": "<view>"
    },
    "name": "tax_lots"
  }
}

Input Schema

NameRequiredDescriptionDefault
viewYes
yearNo
limitNo
offsetNo
symbolNo
symbolsNoNarrow to SEVERAL tickers in one call — the batch form of symbol, up to 25. The two are mutually exclusive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), yet the description adds substantial context beyond them: synthetic shared demo data, that every answer carries activeRules, pagination defaults (limit 1-50, default 10, offset/nextOffset), and that the '…Eur' field twins are deprecated in favor of currency-neutral names. The tax-advice and tax-report caveats are explicit and do not conflict with the annotations.

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?

Front-loaded with the required parameter and ordered logically (views, then filters, then caveats, then deprecation), and essentially every clause carries information. It is, however, one very dense paragraph of semicolon-chained parentheticals, and the closing deprecation note could be compressed without loss.

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?

With six parameters, no output schema, and a 17% schema coverage, return shapes would otherwise be invisible — the description compensates by enumerating the fields and sort order for all four views. What remains thin is the content of activeRules and the exact structure of the ytd response, though both are mentioned.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%, so the description must carry the load and does: each view enum value is unpacked field-by-field (date, daysToExempt, openQty, taxFreeQty, proceedsEur, feesEur, estimatedTaxEur, etc.), filter scope is spelled out per parameter, and limit/offset behavior plus the source of nextOffset is given. The symbol vs symbols mutual exclusivity and the single-ticker vs batch distinction are also made explicit.

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

Purpose5/5

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

States a specific verb and resource ('Read one slice of the illustrative tax-lot orientation (the Taxes tab)') and immediately scopes it against the alternative ('instead of the whole context'). The required 'view' parameter is named up front and each of its four values is described by its distinct content, so an agent can pick the right slice without opening the schema.

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

Usage Guidelines4/5

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

Explains when to use it (read one slice rather than the whole context), which filters apply to which views ('symbol ... or symbols ... filter maturities and openLots; year filters annual'), and adds an explicit when-not ('Approximate orientation only — not tax advice and never input for a tax report'). It stops short of naming a concrete sibling tool as the alternative for whole-context reads.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.