get_signals_recentRecent alt-asset trade signals over a look-back window (days_back).
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| days_back | No |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds scoping context (alt-asset, look-back window) but does not disclose ordering, pagination, or data freshness, which would be useful for interpreting 'recent'.
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?
A single sentence with no filler; the core resource, scope, and key parameter are front-loaded. Every word contributes meaning.
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?
For a read-only, idempotent two-parameter tool with an output schema available, the description is mostly sufficient. The only notable gap is the unstated semantics of limit, which is a minor omission given its conventional meaning and default value.
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 0%, so the description carries the burden for both parameters. It explicitly explains days_back as the look-back window, but does not explain limit's meaning (e.g., maximum number of signals returned), leaving a significant semantic gap.
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?
Description uses specific verb+resource: 'Recent alt-asset trade signals' with a look-back window. This clearly differentiates it from siblings like get_recent_results or get_unread_alerts, which target different data.
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?
The phrase 'recent alt-asset trade signals' implies the intended use case, but no explicit when-to-use or when-not-to-use guidance is given. It does not name alternatives or exclusions, leaving the agent to infer context from the name and sibling list.
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 are distinct, but several pairs overlap in purpose: get_market_data and list_watchlist both return watchlist prices/signals, and the four 'brief' tools have fuzzy boundaries. Descriptions help, but an agent could easily select the wrong one without deeper context.
The dominant verb_noun pattern (get_* for details, list_* for collections) is clear and consistent in style. There are minor deviations like lookup_index_by_brand and run_technical_analysis, and several plural collections use get_, but these remain readable and mostly predictable.
39 tools is well past the 25+ threshold and represents a heavy surface for an agent to navigate. The broad wealth domain explains some of the count, but many granular getters could be consolidated or curated.
The set covers the advertised wealth surface well—portfolio, risk, credit, real assets, markets, geopolitics, watchlist, goals, family, and documents—but it is read-only and lacks obvious navigation endpoints like list_portfolios or detail views for goals/alerts. Agents can retrieve most data, but not all lifecycle operations or entity enumerations are present.