Skip to main content
Glama
Sign In

Stock Compass

by io.github.Stock-Compass
OverviewDiscussionsAdmin

Set stop and target

set_stop_target
DestructiveIdempotent

Sets the stop and/or target in force on the open position, as the stop/target form on the page does. 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>"
    },
    "name": "set_stop_target"
  }
}

Input Schema

NameRequiredDescriptionDefault
stopNoStop price; null clears it.
marketYeshk = Hong Kong, us = United States, cn = China A-shares.
targetNoTarget price; null clears it.
tickerYesFor example 0700.HK or 700 (hk), AAPL (us), 600519.SS or 600519 (cn).
preview_idNoThe preview_id that the same call without it returned. Without it, nothing is changed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

The description provides vital behavioral context missing from the annotations. It details the core mechanism of the tool: sending without a preview_id initiates a read-only preview, while sending it with the matching ID executes the change.

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?

The description is highly dense but efficient, using two sentences to explain both the primary function and the complex, multi-step invocation workflow. It is appropriately sized.

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?

Since the action is destructive (destructiveHint: true) and lacks an output schema for immediate feedback, the description is maximally complete by explaining the required preview-execution pattern. No critical execution detail is omitted.

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 description coverage is 100%, so parameter definitions are solid. The description adds a baseline level of semantic meaning by clarifying that sending null for stop or target 'clears' that setting, adding useful operational context.

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 tool clearly defines its function: 'Sets the stop and/or target in force on the open position.' It avoids vagueness and points to the specific financial context.

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?

While there are no sibling comparisons, the description provides critical operational guidelines regarding the workflow. It explicitly states that the call must be made twice—once for preview, once for execution.

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

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