Jornalo — futures trading journal

Set the notes, quality grade and/or validation status on one trade. Only the fields you pass are written, and each one replaces its previous value (read the current notes first if you mean to append); an empty notes string clears them. By default the same fields are copied to the trade's mirrors in the user's other accounts (mirroredTo lists them).

Find the trades that were open on a given calendar day — to match a screenshot, a note or a question like 'my ZN trade on 27 March' to a real trade id. date (YYYY-MM-DD) is read in the user's configured timezone (override with timezone, an IANA name); a trade matches when its [entry, exit] window touches that day, so multi-day swings match every day they were open; toleranceDays (0-3) widens the window — report the date difference to the user when you rely on it. symbol matches the instrument family, micro ≡ mini (GC finds MGC, 6B finds M6B, NQ finds MNQ). Optional accountId (comma-separated, from list_accounts) and side. Results include local entry/exit times, the existing images and the mirrored copies in other accounts. If two trades of the same family match the same day, ask the user or read the chart's time axis — never pick one silently.

Upcoming macro releases in time order (high impact worldwide; medium for USD, EUR, GBP, JPY, AUD, CAD, CHF, NZD, CNY; plus CFTC positioning), from Jornalo's calendar refreshed every 30 minutes. Covers this week and next. Each event has at (UTC) and local (the user's timezone); releases from the last hour stay in so their actual can be read.

Daily and cumulative net P&L over a period, for trend and drawdown questions.

Net P&L, profit factor and RoMaD broken down by calendar month.

Headline trading KPIs for a period: net P&L, win rate, profit factor, expectancy, max drawdown, Sharpe and Sortino. Start here for "how am I doing?".

For each active prop-firm account: how much cushion is left before the trailing drawdown and the daily loss limit liquidate it, the alert level, progress to the profit target and the recommended risk per trade. This is the answer to "how close am I to blowing the account?".

Net P&L, win rate, profit factor and expectancy per setup — which strategies earn and which bleed.

Every trading account: broker/prop-firm account id, prop firm, category (evaluation | funded | live), account type, status (active | inactive | unlinked), first and last trade dates and trade count. Users refer to accounts loosely — "the 996", "my Apex funded", "the Lucid eval", "the one ending in 863": resolve against this list by id suffix, prop firm and category; if more than one account fits, ask which one instead of guessing. Ids feed the other tools.

Recent trades with their trade ids, current setups and whether they already have notes. Call this before tagging or annotating so you use real ids.

The user's setup/tag vocabulary with how many trades carry each one.

Individual trades for a period, newest first or ranked by net P&L, each with its attached screenshots (images). Optional symbol filters by instrument family (micro ≡ mini). To find what was open on a specific calendar day use find_trades.

Get single-use upload URLs to attach chart screenshots to one trade. The image bytes are NOT sent through this tool — tool arguments cannot carry megabytes of base64 — so call it, then have your runtime HTTP PUT the raw file body to each uploadUrl within 15 minutes (e.g. curl --data-binary @file) with Content-Type image/png, image/jpeg or image/webp; max 4 MB per image, 6 images per trade. One ticket = one image: pass one label per file (e.g. ['Ejecución','Análisis']). By default the screenshot is also attached to the same trade mirrored in the user's other copier accounts (mirror=false to skip). Before calling: ask the user where the files are and which account they belong to, match each file to a trade with find_trades, check the trade's existing images so re-runs do not create duplicates, and confirm the mapping with the user. Requires a client that can read local files and make HTTP requests.

Replace the setups on one trade. Setups are given by name and must already exist — call list_setups first. Replaces, does not append: to add one, send the trade's current setups plus the new one. By default the trade's mirrors in the user's other accounts get the same setups (mirroredTo lists them).