get_market_opens[DRILL-DOWN] Latest TradFi market open prices for BTC/ETH/SOL across sessions. Source: watchers.market_opening_watcher.get_latest_opens(). Same data as REST /market-opens.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| market_opens | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description confirms the read-only nature by describing retrieval of prices. It adds useful context about the data source and equivalence to a REST endpoint, but doesn't disclose additional behavioral traits such as freshness guarantees or pagination.
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 a single sentence that efficiently conveys the data type, scope, source, and equivalence to an existing endpoint. Every piece of information earns its place with no repetition or fluff.
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?
With no parameters, a read-only annotation, and an output schema present, the description provides sufficient information for an agent to select and invoke the tool. It covers what data is returned, the source, and the equivalence to a known REST endpoint.
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?
The tool has zero parameters, and the schema reflects this with 100% coverage. The description correctly omits parameter details, matching the baseline expected for parameterless tools.
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 states the tool retrieves the latest TradFi market open prices for BTC/ETH/SOL across sessions. The 'DRILL-DOWN' tag and reference to REST endpoint distinguish it from broader market data tools.
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?
No explicit guidance on when to use this tool versus its siblings. The 'DRILL-DOWN' label implies a focused use case, but no alternatives are named or contrasted, leaving the agent to infer appropriateness.
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 with detailed descriptions, but there are clusters of similar concepts (e.g., get_liquidity_map vs get_liquidation_map, get_state vs get_state_brief, multiple signal-related tools) that could cause misselection despite thorough documentation.
All tools follow a consistent lowercase verb_noun pattern, predominantly get_* nouns, with only a few non-get verbs like list_signals, rank_trades, log_trade, etc., but the style is uniform.
With 52 tools, the surface is extremely heavy for an agent to navigate. While the server's scope is broad, the count far exceeds the typical 3-15 range and falls into the 'too many' category.
The tool set covers the full lifecycle for journaling, signals, market analysis, and proof, with no major dead ends. Minor gaps exist, such as no dedicated get_trade_by_id (workaround via get_journal) and no get_market_state tool despite being referenced in get_state.