Manawa Terminal

Create price alert

create_alert

Create a price or event alert for a symbol.

Args:
    symbol: Stock symbol (e.g. "AAPL")
    alert_type: "target_price", "movement_pct", or "event"
    direction: Required for price alerts — "above", "below", or "either"
    threshold: Required for price alerts — price level or percentage move
    notes: Optional description
    event_types: Required when alert_type is "event". One or more of:
        "earnings_transcript", "insider_trade", "news_stock", "press_release",
        "filing_8k", "filing_13f", "politician_senate", "politician_house",
        "merger_acquisition"

Input Schema

TableJSON Schema

Name	Required	Description	Default
`notes`	No
`symbol`	Yes
`direction`	No
`threshold`	No
`alert_type`	Yes
`event_types`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

TDQS

A4.8/5.0

Behavior5/5

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

The description goes beyond the minimal annotations by specifying conditional requirements for different alert types (direction/threshold for price alerts, event_types for event alerts) and enumerating all accepted event types. This gives concrete behavioral expectations that annotations do not provide.

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 a well-structured docstring with a clear one-line summary followed by a compact parameter list. Each entry is concise, and the whole is scannable without unnecessary prose.

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?

For a tool with six parameters and conditional logic, the description is thorough: it covers all parameters, their types, required-ness based on alert_type, and the full set of event types. It is complete enough for an agent to invoke the tool correctly without further clarification.

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 zero schema description coverage, the description fully compensates by explaining each parameter's meaning, conditions, and even providing an example for symbol. It also lists all valid event_types, which the schema does not enumerate.

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 uses the specific verb 'Create' and clearly identifies the resource as a 'price or event alert', which distinguishes it from sibling tools like list_alerts and delete_alert. The expanded scope beyond the title's 'price alert' is still specific and meaningful.

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?

The description clearly implies when to use this tool: to create a new price or event alert. It does not explicitly name alternatives or exclusions, but the unique purpose and sibling context make the use case obvious, though not as explicit as it could be.

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?