Skip to main content
Glama

mv_get_curator_portfolio

Aggregate MetaVaults from a curator into a portfolio view with total AUM, blended APY, projected fee revenue, and cross-vault signals. Input by curator address, label, or explicit vault list.

Instructions

Aggregate multiple MetaVaults managed by a single curator into one portfolio view.

Three input modes (priority: explicit > label > address):

  1. Explicit mode: metavault_addresses as a JSON array of {chain, address} pairs to aggregate specific vaults (machine-friendly).

  2. Label mode: curator_label="Gami Labs" — resolves to the union of curator EOAs whose curator.name matches case-insensitively across chains. Solves the named-curator-multiple-EOAs case (e.g. Gami Labs has different EOAs on base vs flare).

  3. Address mode: curator_address=0x... — scans all chains for MetaVaults where the curator's address matches the vault's curator.addresses array (machine-friendly when the EOA is known).

Returns:

  • Total AUM across all vaults

  • Blended APY (TVL-weighted)

  • Projected annual fee revenue at the configured curator fee

  • Concentration by underlying asset and by chain (suppressed for single-vault curators)

  • Per-underlying rollup with expiry calendar (suppressed for single-underlying curators)

  • Per-vault summary with position count and per-vault action items

  • Cross-Vault Items: GENUINE cross-vault signals computed by aggregation (suppressed when no genuine signal fires — silent on clean is first-class)

Use spectra_get_curator_dashboard for deep-dive into a specific vault. Use morpho_monitor_risk for Morpho position health across the curator's address. Use spectra_stress_test_vault for withdrawal simulation on a specific vault.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
curator_addressNoCurator wallet address. Scans all chains for MetaVaults managed by this address. Machine-friendly when the EOA is known.
curator_labelNoCurator display name (e.g. 'Gami Labs'). Resolves case-insensitively to the union of curator EOAs across chains. Use when a curator brand spans multiple EOAs (Gami Labs has different EOAs on base vs flare).
metavault_addressesNoExplicit list of MetaVault {chain, address} pairs to aggregate. Takes priority over label/address.
curator_fee_pctNoCurator performance fee as % of vault yield (default 10%). Used for fee revenue projection.
Behavior5/5

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

No annotations provided, so description fully discloses behavior: input modes, case-insensitive label resolution, cross-chain scanning, suppression rules for single-vault/single-underlying curators, and silent handling of no genuine signals. 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?

Well-structured with numbered modes and bullet-point return fields. Every sentence provides essential information. Front-loaded with purpose. Efficient use of ~200 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?

Despite no output schema, description thoroughly lists all return fields (AUM, APY, fee revenue, concentration, per-vault summary, cross-vault items) with conditions. Covers input modes, edge cases, and suppression rules. Complete for agent decision-making.

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

Parameters5/5

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

Schema coverage is 100% but description adds significant context: explains three input modes and their priority, clarifies curator_label resolves case-insensitively across chains, and details curator_fee_pct default and purpose. Adds value beyond schema.

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?

The description clearly states the tool aggregates multiple MetaVaults into a portfolio view, with specific verb 'Aggregate' and resource 'MetaVaults'. It distinguishes from siblings like spectra_get_curator_dashboard and morpho_monitor_risk.

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

Usage Guidelines5/5

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

Explicitly describes three input modes with priority order (explicit > label > address). Provides use cases for each mode and references sibling tools for alternative actions (deep-dive, risk monitoring, stress test).

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/Finanzgoblin/spectra-mcp-server'

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