get_portfolio_driftDrift of a portfolio versus its target allocation.
| Name | Required | Description | Default |
|---|---|---|---|
| household_id | Yes | ||
| portfolio_id | Yes |
| 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 the safety profile is covered. The description adds semantic context by defining drift as being relative to target allocation, but it discloses no additional behavioral traits such as calculation basis, time period, or output characteristics.
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 concise sentence with no fluff or repetition. It front-loads the core concept immediately. Minor deduction because it is a sentence fragment and could have used the space to add parameter or usage context without becoming verbose.
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 simple read-only tool with an output schema and strong safety annotations, the description is minimally viable. However, it leaves required parameters undocumented and does not resolve ambiguity with get_drift_snapshot, so an agent may still need external context to call it confidently.
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 does not explain household_id or portfolio_id. The word 'portfolio' hints at portfolio_id's role, but the description does not clarify the relationship between the two required parameters or their formats. With low schema coverage, the description needed to compensate and did not.
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 identifies the resource (portfolio) and the specific metric (drift versus target allocation), which separates it from positions/risk/summary. However, it is a noun phrase rather than an explicit verb+resource statement, and it does not distinguish itself from the closely named sibling get_drift_snapshot.
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?
There is no guidance about when to use this tool versus alternatives. In particular, the sibling get_drift_snapshot likely overlaps, but the description provides no differentiation or exclusion criteria. The use case is only implied by the name and noun phrase.
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.