Stock Compass

Create a price alert

create_price_alert

Creates a price alert that fires when the price goes above or below the threshold. Sent without preview_id, it changes nothing and returns a preview of the change with a preview_id; sent again with the same arguments and that preview_id, it makes the change.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "market": "<market>",
      "ticker": "<ticker>",
      "direction": "<direction>",
      "threshold": "<threshold>"
    },
    "name": "create_price_alert"
  }
}

Input Schema

Name	Required	Description
`note`	No
`market`	Yes	hk = Hong Kong, us = United States, cn = China A-shares.
`ticker`	Yes	For example 0700.HK or 700 (hk), AAPL (us), 600519.SS or 600519 (cn).
`direction`	Yes
`threshold`	Yes	The price.
`preview_id`	No	The preview_id that the same call without it returned. Without it, nothing is changed.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 31, 2026

TDQS

A3.9/5.0

Behavior4/5

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

The preview-then-confirm protocol is the key non-obvious behavior and it is disclosed explicitly, including the fact that the first call mutates nothing. This adds real value beyond the annotations (readOnlyHint=false, idempotentHint=false, destructiveHint=false). It stops short of saying what happens on duplicate alerts, whether the preview expires, or what the response contains.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences with no filler, and the purpose is front-loaded before the preview mechanics. The second sentence is somewhat convoluted with nested clauses about preview_id, but every part carries 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 a 6-parameter mutation with an unusual two-call commit pattern and no output schema, the definition covers the essential contract: what is created, what the first call returns, and how to finalize. Remaining gaps (return payload shape, alert lifecycle, duplicate handling) are meaningful but secondary.

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 coverage is 67% and the schema already documents market, ticker, threshold, and preview_id in detail. The description mainly restates preview_id's role ("same arguments and that preview_id") and implies the above/below semantics of direction, adding only marginal meaning beyond the structured fields.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Creates a price alert") plus the triggering condition ("fires when the price goes above or below the threshold"). It reads clearly as the write counterpart to get_price_alerts, but never names that sibling, so the differentiation is inferred rather than stated.

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 concrete procedural guidance for the two-phase flow: call without preview_id to get a preview, then repeat with the same arguments plus preview_id to commit. It does not say when to prefer this over siblings like set_stop_target or add_to_watchlist, nor any limits on the number of alerts.

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

All Stock Compass 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.