Equibles

Update Portfolio Lot

UpdatePortfolioLot

Correct a lot the USER already recorded: a mistyped quantity, price, trade date, note or exchange rate. Only the fields you pass change; the rest are left alone.

The instrument itself cannot be edited: a lot on the wrong stock or the wrong contract is a different holding, so remove it with RemovePortfolioLot and add the right one. To record a sale, use ClosePortfolioLot rather than editing the quantity down, because editing it away loses the realized profit.

Input Schema

Name	Required	Description
`note`	No	Optional. A replacement note, up to 256 characters.
`lotId`	Yes	The lot id shown by GetMyPortfolio, e.g. a1b2c3d4.
`fxRate`	No	Optional. The broker's exchange rate on the trade, as units of the portfolio's currency per 1 unit of the lot's currency.
`quantity`	No	Optional. The corrected signed size. Negative is a short or written option.
`portfolio`	Yes	The portfolio holding the lot, by name.
`clearFxRate`	No	Optional. True removes the broker's exchange rate, so the lot converts at the official rate on its trade date. Cannot be combined with fxRate.
`costPerUnit`	No	Optional. The corrected price per share, always positive.
`acquiredDate`	No	Optional. The corrected trade date, as yyyy-MM-dd.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026

addedInput schema / properties / clearFxRate

Added value: +{
+  "default": false,
+  "description": "Optional. True removes the broker's exchange rate, so the lot converts at the official rate on its trade date. Cannot be combined with fxRate.",
+  "type": "boolean"
+}

addedInput schema / properties / fxRate

Added value: +{
+  "default": null,
+  "description": "Optional. The broker's exchange rate on the trade, as units of the portfolio's currency per 1 unit of the lot's currency.",
+  "type": [
+    "number",
+    "null"
+  ]
+}

AddedAug 18, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false, openWorldHint=false, so the safety profile is partly covered. The description still adds real value beyond them: partial-update semantics ('only the fields you pass change'), the immutability of the instrument, and the consequence that editing quantity down loses realized profit. It omits permission/auth requirements, which is a minor gap.

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?

Three tight sentences, front-loaded with the core action and scope, then the two routing rules. No filler; every clause carries decision-relevant information.

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 an 8-parameter mutation tool with no output schema, the description covers partial-update behavior, the immutable instrument, and sibling routing, which is most of what an agent needs. It does not state what the response looks like or whether success is confirmed, a minor omission.

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 every parameter is documented in the schema, which sets the baseline at 3. The description frames why each field exists (mistyped quantity, price, trade date, note, exchange rate) but adds no syntax or format detail beyond what the schema already carries.

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 (correct) and resource (a lot the USER already recorded), enumerating the fields that can be fixed. It distinguishes itself from AddPortfolioLot, RemovePortfolioLot, and ClosePortfolioLot by name, so an agent can pick it without opening schemas.

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?

Explicitly routes the agent: use RemovePortfolioLot for a wrong instrument, use ClosePortfolioLot instead of editing quantity down for a sale. This is exactly the when/when-not/alternative guidance that most definitions lack.

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

All Equibles tools Inspect

Try in Browser