Manawa Terminal

Create alert

create_alert

Create a price alert, an event alert, or a clock.

Calling this stores the alert. A clock may omit the ticker.

Args:
    symbol: Stock symbol (e.g. "AAPL"). Required for price and event alerts. Optional for a clock.
    alert_type: "target_price", "movement_pct", "event", or "schedule"
    direction: Required for price alerts — "above", "below", or "either"
    threshold: Required for price alerts — price level or percentage move
    notes: Optional description. Not the agent instruction.
    event_types: Required when alert_type is "event". Live-tape ids such as
        filing_13f, politician_senate, options_unusual, ipo_upcoming.
    event_filters: Optional slices. Example: {"politician_senate": {"type": ["purchase"]}}.
        An omitted field matches every value.
    name: Optional title. Blank is filled from the rule.
    agent_instruction: What the agent does when this fires. Empty means notify only.
    max_fires: How many fires before it leaves Active. Omit to keep a repeating alert firing.
    schedule_at: ISO time. Required when alert_type is "schedule".
    schedule_tz: IANA zone. UTC when omitted.
    schedule_repeat: once, daily, weekdays, weekly, or monthly. Default once.

Input Schema

Name	Required	Description	Default
`name`	No
`notes`	No
`symbol`	No
`direction`	No
`max_fires`	No
`threshold`	No
`alert_type`	No
`event_types`	No
`schedule_at`	No
`schedule_tz`	No
`event_filters`	No
`schedule_repeat`	No
`agent_instruction`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedOct 11, 2026

addedInput schema / properties / agent_instruction

Added value: +{
+  "default": "",
+  "title": "Agent Instruction",
+  "type": "string"
+}

addedInput schema / properties / alert_type / default
```
Added value: +""
```

addedInput schema / properties / event_filters

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": true,
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Event Filters"
+}

addedInput schema / properties / max_fires

Added value: +{
+  "anyOf": [
+    {
+      "type": "integer"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Max Fires"
+}

addedInput schema / properties / name

Added value: +{
+  "default": "",
+  "title": "Name",
+  "type": "string"
+}

addedInput schema / properties / schedule_at

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Schedule At"
+}

addedInput schema / properties / schedule_repeat

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Schedule Repeat"
+}

addedInput schema / properties / schedule_tz

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "title": "Schedule Tz"
+}

addedInput schema / properties / symbol / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / symbol / default
```
Added value: +null
```
removedInput schema / properties / symbol / type
```
Removed value: -"string"
```

removedInput schema / required

Removed value: -[
-  "symbol",
-  "alert_type"
-]

First observedAug 5, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, but the description adds real behavior beyond them: 'Calling this stores the alert,' the lifecycle rule that max_fires controls when an alert 'leaves Active' (omitting it makes it repeat forever), and that empty agent_instruction means notify-only. It does not cover permissions or rate limits, so not a 5.

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?

Front-loaded one-line purpose, then a dense Args block where every line earns its place because the schema has no descriptions of its own. No filler or repetition despite documenting 13 parameters.

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?

Given 13 mostly-optional parameters, 0% schema coverage, and an existing output schema (so return format need not be explained), the description supplies every per-type requirement, default, and enum an agent needs to construct a valid call. Nothing material is missing.

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?

Schema description coverage is 0% across 13 parameters, so the description carries the full burden and does so thoroughly: it supplies the alert_type enum values, the schedule_repeat enum (once/daily/weekdays/weekly/monthly) with default, direction values, example event_types ids, event_filters example with matching semantics, and the disambiguation 'notes ... Not the agent instruction.'

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?

Opens with a specific verb and the three concrete resource types it creates (price alert, event alert, clock), which cleanly separates it from list_alerts and delete_alert in the sibling set. An agent knows exactly what this tool produces without opening the schema.

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?

Gives strong conditional guidance: which fields are required per alert_type (direction/threshold for price, event_types for event, schedule_at for schedule) and that a clock may omit the ticker. It never names an alternative tool or an explicit when-not-to-use condition, so it stops short of a 5.

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

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?