Skip to main content
Glama

track_asset

Idempotent

Add or update a financial asset in your tracked list to control which symbols are covered by committee analysis and DCA investment jobs.

Instructions

Add a symbol to the tracked-asset list, or update an existing entry (idempotent upsert: only the fields you pass are changed). The tracked list decides which symbols the committee and DCA jobs cover.

Use when the user says "track AAPL" or wants to change a tracked asset's cap/channel/fees.

Args: symbol: yfinance ticker to track (e.g. "AAPL", "0700.HK", "BTC-USD"). max_single_invest_cny: Per-decision investment cap in CNY. Required when creating a new entry; optional on update. display_name: Human-friendly name shown in reports. channel: Where the user actually buys it (broker/app name). price_offset_pct: Systematic offset between the quote and the user's actual fill price, in percent (e.g. bank gold spread). sell_fee_pct: Sell-side fee in percent, used by fee-aware math.

Returns: The stored asset entry, or {"status": "error", "error": ...}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesyfinance ticker to track, e.g. 'AAPL', '0700.HK', 'BTC-USD'.
channelNoWhere the user actually buys it (broker/app name).
display_nameNoHuman-friendly name shown in reports.
sell_fee_pctNoSell-side fee in percent, used by fee-aware math.
price_offset_pctNoSystematic offset between quote and actual fill price, in percent (e.g. bank gold spread).
max_single_invest_cnyNoPer-decision investment cap in CNY. Required when creating a new entry; optional on update.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

Idempotent upsert behavior is clearly stated and matches annotation (idempotentHint=true). Gives extra detail: 'only the fields you pass are changed', and notes that 'max_single_invest_cny' is required on create but optional on update. No contradiction.

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 with purpose and idempotency, then usage case, then parameter list. Every sentence adds value; no fluff. Well-structured.

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?

Fully explains the tool's purpose, behavior, parameter details, and return format (stored asset entry or error). Output schema is present, so return values are covered. Complete for a complex tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema already covers all parameters (100% coverage), but the description adds context beyond schema: e.g., explains that 'max_single_invest_cny' is required on creation and optional on update, and clarifies the purpose of 'channel' and 'price_offset_pct'.

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?

Clearly states 'Add a symbol to the tracked-asset list, or update an existing entry'. Distinguishes from sibling 'untrack_asset' by being an upsert, not a removal. Provides context that tracked list decides coverage for committee and DCA jobs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says 'Use when the user says "track AAPL" or wants to change a tracked asset's cap/channel/fees.' Implies not for removal (since 'untrack_asset' sibling exists).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/longsizhuo/openInvest'

If you have feedback or need assistance with the MCP directory API, please join our Discord server