Monitor real-time prices and performance metrics for a portfolio of cryptocurrency holdings. Returns current price per coin, 24-hour percentage change, portfolio value summary, and top movers. Use for active portfolio management and price monitoring.
| Name | Required | Description | Default |
|---|---|---|---|
| coins | Yes | List of cryptocurrency codes in portfolio to track real-time |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, covering the safety profile. The description adds behavior details: real-time data and specific output metrics (price, 24h change, portfolio value, top movers). However, it does not disclose limitations like data source reliability, rate limits, or behavior for invalid symbols.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is two sentences, front-loaded with the core action and outputs. Every sentence earns its place with no redundancy or filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the simple one-parameter schema and no output schema, the description adequately covers the return values and use case. It lists the specific outputs (current price, 24h change, portfolio value, top movers), making it complete for this level of complexity.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, with the 'coins' parameter clearly documented as cryptocurrency symbols. The description adds no additional parameter semantics beyond reinforcing the portfolio context, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly specifies the tool's function: monitoring real-time cryptocurrency portfolio prices and performance metrics. It differentiates from sibling tools like get_crypto_prices by emphasizing portfolio-level outputs such as value summary and top movers, not just individual prices.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly states 'Use for active portfolio management and price monitoring', providing a clear use case. However, it does not contrast with alternative tools like get_crypto_prices or mention when not to use it, so it falls 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.
Add one secure layer between your agents and this server.
Most tools have clearly distinct purposes: crypto prices, exchange rates, stock data, stock screening, and crypto portfolio tracking. However, get_crypto_prices and track_crypto_portfolio both return crypto price data, and get_stock_data and screen_stocks are related but distinct in action.
All tool names follow a consistent verb_noun pattern in snake_case (get_, screen_, track_). The 'get_' prefix is used for three tools, with 'screen_' and 'track_' as appropriate action verbs. No mixed conventions.
Five tools is well-scoped for a finance server covering cryptocurrencies, exchange rates, and stocks. Each tool earns its place, covering core data retrieval and screening functions without unnecessary bloat.
The tool set covers key finance use cases: price lookups, screening, and portfolio tracking. Minor gaps exist, such as no historical price data or stock portfolio tracking, but the primary domain is well-served.