get_recent_resultsRecent auction-realised and list-price events over a look-back window.
| 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 the operation read-only, idempotent, and non-destructive. The description adds a time-window behavior ('look-back window'), but does not disclose ordering, pagination, or event semantics. No contradiction with annotations.
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?
One sentence, no filler, key fact front-loaded. Every word earns its place.
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?
Low complexity (2 optional params, no nested objects), rich annotations, and an output schema reduce the burden on the description. The sentence provides enough orientation for an agent to invoke it; the main gap is the missing guidance on when to choose it over siblings.
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?
With 0% schema description coverage, the description carries most of the burden. 'Look-back window' gives meaning to days_back, but limit is not explained, and the string/number format is not addressed. The property names themselves provide some help, but the description only partially compensates.
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 uses a specific verb ('get') and identifies a concrete resource: 'auction-realised and list-price events over a look-back window.' This is much clearer than the generic title, though it does not explicitly differentiate it from sibling tools like get_signals_recent or get_market_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 description implies the tool is for retrieving recent price/event history over a configurable window, but it provides no explicit guidance on when to prefer it over similar get_* siblings or what alternatives exist. There are no exclusions or use-case scenarios.
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.