get_real_asset_economicsReal-asset economics — income, costs, net cashflow and net yield.
| Name | Required | Description | Default |
|---|---|---|---|
| household_id | 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 communicate that this is read-only, idempotent, and non-destructive, so the safety profile is covered. The description adds the semantics of what economics includes, but it does not disclose aggregation level, scope of an empty household_id, or any other behavioral traits beyond the enumerated output fields.
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 compact sentence with the core content front-loaded via an em-dash. It contains no filler or redundant restatement of the tool name.
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?
The output schema covers return details and the annotations cover safety, so the description is adequate for a simple read-only tool. However, it lacks important context about when to call it, how the optional household_id behaves, and how it relates to sibling tools like get_real_asset. It is minimally viable but has clear gaps.
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%, and the description makes no mention of household_id. The agent must rely on the parameter name alone to infer it selects a household, and there is no guidance about the default empty string or whether it is optional. The description fails to compensate for the schema's lack of documentation.
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 defines the tool's resource as 'real-asset economics' and lists the specific computed fields: income, costs, net cashflow, and net yield. This makes the purpose reasonably clear and distinguishes it from related tools like get_real_asset, though it lacks an explicit verb and direct sibling differentiation.
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 guidance is given about when to use this tool versus alternatives such as get_real_asset, get_household_aum, or get_net_worth. There is also no explanation of how the optional household_id parameter affects the result or what an empty value means.
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.