Skip to main content
Glama

equibles

by io.github.daniel3303

Update Portfolio Lot

UpdatePortfolioLot

Correct a lot the USER already recorded: a mistyped quantity, price, trade date or note. 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

TableJSON Schema
NameRequiredDescriptionDefault
noteNoOptional. A replacement note, up to 256 characters.
lotIdYesThe lot id shown by GetMyPortfolio, e.g. a1b2c3d4.
quantityNoOptional. The corrected signed size. Negative is a short or written option.
portfolioYesThe portfolio holding the lot, by name.
costPerUnitNoOptional. The corrected price per share, always positive.
acquiredDateNoOptional. The corrected trade date, as yyyy-MM-dd.

TDQS

A4.9/5.0
Behavior5/5

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

The description clearly states that only passed fields are updated ('the rest are left alone'), despite annotations being empty (no readOnlyHint, destructiveHint, or openWorldHint). It also warns that editing away quantity loses realized profit, adding critical behavioral context.

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?

The description is highly concise and logically structured. It opens with the core purpose, then the 'instrument cannot be edited' rule, followed by the 'sale vs. correction' distinction. Every sentence serves a purpose without fluff.

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

Completeness5/5

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

The description is complete for a mutation tool with no output schema. It explains the update mechanism, immutable fields, and related sibling tools. Given the context signals (no output schema, 100% schema coverage), no further return-value details are needed.

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

Parameters4/5

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

Schema coverage is at 100%, so all parameters are documented structurally. The description adds value by clarifying the semantics of not passing fields (they remain unchanged) and explaining the business rule for quantity signs (negative for shorts/written options). A 4 is appropriate, but not a 5, as no further nuance is needed.

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?

The description clearly specifies the tool's purpose: to correct user-recorded lot details like quantity, price, trade date, or note. It explicitly distinguishes this from deleting lots (use RemovePortfolioLot) or recording sales (use ClosePortfolioLot), and states what cannot be changed (instrument).

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?

The description explicitly guides when NOT to use the tool (i.e., for wrong instruments—use RemovePortfolioLot instead) and what to use for sales (ClosePortfolioLot). This directly addresses alternatives and typical misuses.

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

All equibles toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.4/5.0
Disambiguation4/5

Most tools have clearly distinct purposes, with detailed descriptions that cross-reference related alternatives. A few near-duplicate names could cause misselection, notably SearchDocument versus SearchDocuments and GetCftcPositioning versus GetLatestCftcPositioning.

Naming Consistency5/5

Tool names consistently follow a VerbNoun camelCase pattern: Get for retrievals, Search for discovery, List/Read for document access, and Add/Close/Remove/Update/Watch/Create/Delete for portfolio mutations. Despite the large count, there is no mixing of naming conventions or unpredictable verb styles.

Tool Count1/5

108 tools is an extreme surface area, far beyond the 3-15 well-scoped range and well past the 25+ threshold. Even for a broad financial data platform, this creates a heavy selection burden and substantial context overhead for agents.

Completeness4/5

The server covers an unusually wide domain: prices, fundamentals, SEC filings, options, insider activity, 13F holdings, short interest, macro data, funds, IPOs, and full portfolio lifecycle management. Notable gaps remain, such as a basic company profile/ticker-resolution tool, dividend history, and analyst estimates, so it is not a perfect 5.

Resources