Skip to main content
Glama

discover_gaps

Read-onlyIdempotent

Identifies portfolio gaps where asset allocation is below 3% of market value and suggests largest low-cost ETFs to fill them.

Instructions

Roles the user's portfolio is light in (≤3% of market value) and the largest low-cost ETFs that fill each (offline, read-only, propose-only). Use to answer 'what am I missing / what could I consider adding'. The candidate listing is deterministic; for the full per-candidate screen call screen_candidate.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
asofYes
gapsYes
noteNoRoles your book holds ≤3% of, with the biggest funds for each — propose-only, never a prediction. For the full screen (cost / liquidity / overlap / did-it-diversify-your-drawdowns) call `screen_candidate`. Read-only: figures are derived from your transaction log and the on-disk price cache. Uncached prices are fetched online on demand — a one-time core warm on the first cold call, plus any new ticker you ask about (set ASSET_MCP_OFFLINE=1 to keep it strictly offline); a value still unavailable shows null (n/a), never a guess. This is a view, not financial advice.
unpriced_holdingsNoheld tickers with no cached price — role exposure (and thus the gaps) may be skewed; warm the cache for the full picture
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, openWorldHint, idempotentHint. Description adds value by stating the tool is 'offline' and 'propose-only', and that the candidate listing is deterministic. No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences that front-load the main action and include thresholds, output description, and referral to a sibling tool. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With zero parameters and an existing output schema, the description is fully adequate. It explains the gap threshold, the nature of the output, and how to get more detailed screening.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters; schema description coverage is 100% (vacuously). Baseline score of 4 is appropriate as the description adds no parameter detail beyond the schema, but none is needed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states the tool discovers portfolio gaps (under 3% market value) and suggests largest low-cost ETFs. The verb 'discover gaps' is specific, and it distinguishes from sibling tool screen_candidate by directing users there for full candidate details.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Description explains when to use: 'Use to answer what am I missing / what could I consider adding'. It also notes the tool is offline, read-only, and propose-only, and advises to use screen_candidate for per-candidate details. No explicit when-not, but guidance is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/disin7c9/asset-management'

If you have feedback or need assistance with the MCP directory API, please join our Discord server