Manawa Terminal

Add portfolio transaction

add_transaction

Add a buy, sell, deposit, or withdrawal transaction to a portfolio.

Args:
    portfolio_id: The portfolio UUID
    symbol: Stock symbol (e.g. "AAPL"). For deposit/withdrawal use "$CASH"
        (aliases "CASH" / blank are normalized to "$CASH").
    side: "buy", "sell", "deposit", or "withdrawal"
    qty: Number of shares (or cash amount for deposit/withdrawal)
    price: Price per share
    date: Transaction date (YYYY-MM-DD)

Input Schema

TableJSON Schema

Name	Required	Description	Default
`qty`	Yes
`date`	Yes
`side`	Yes
`price`	Yes
`symbol`	Yes
`portfolio_id`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.6/5.0

Behavior4/5

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

The description adds behavioral detail beyond the annotations by explaining that symbol aliases 'CASH' and blank are normalized to '$CASH', and that qty represents cash amount for deposits/withdrawals. It also specifies the date format (YYYY-MM-DD). This provides useful context that annotations don't convey, though it doesn't mention side effects like portfolio balance updates.

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 compact and front-loaded with the main purpose, followed by a structured Args block. Each line adds necessary information, with no filler or redundancy. It strikes a good balance between completeness and brevity.

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 6-parameter tool: it covers all required arguments, provides examples and normalization rules, and clarifies the interpretation of qty across transaction types. An output schema exists, so return-value details are not needed. It lacks only minor preconditions (e.g., portfolio existence), which are likely evident.

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?

With 0% schema description coverage, the description fully compensates by listing all 6 parameters and their meanings. It explains the special symbol handling for cash transactions and distinguishes qty semantics by side (shares vs cash amount). This is exemplary parameter documentation.

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 opens with a specific verb and resource: 'Add a buy, sell, deposit, or withdrawal transaction to a portfolio.' It clearly identifies the action and object, and the transaction types distinguish it from sibling tools that create other resources (e.g., create_portfolio, create_watchlist).

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?

It doesn't explicitly state when not to use it or name alternatives, but the description provides clear context: it's for adding any of four transaction types to a portfolio. The parameter guidance (e.g., cash handling) reinforces the intended use case. Since there is no competing sibling tool for adding transactions, this is sufficient.

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

All Manawa Terminal tools Inspect

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

A3.8/5.0

Disambiguation5/5

Each tool targets a distinct resource and action. Portfolio, alert, watchlist, library, journal, and search tools have clearly separated purposes with no overlapping functionality. Even similar tools like get_portfolio_statistics and get_positions provide different outputs.

Naming Consistency4/5

The majority follow a clear verb_noun pattern in snake_case (e.g., create_portfolio, delete_library_item). However, 'finance_search' inverts the verb-noun order and 'run_deepdive' uses a less common verb, creating minor but noticeable exceptions.

Tool Count4/5

31 tools is on the high side but each serves a distinct purpose across portfolio management, alerts, watchlists, library, journal, search, and bug reporting. The library subsystem alone accounts for 11 tools (CRUD + versions + move + rename + search), which is justifiable for a full document manager.

Completeness3/5

Core operations are present but several lifecycle gaps exist: no delete_watchlist, delete_portfolio, update_portfolio, update_alert, or delete_transaction. The journal and deepdive areas also lack update/delete capabilities. Agents may hit dead ends when trying to remove or modify certain resources.

Resources

Need Help?