Skip to main content
Glama

get_daily_briefing

Read-onlyIdempotent

Generates a structured and narrative briefing of your crypto portfolio: total value, top movers, Aave health alerts, and activity counts over 24h, 7d, or 30d.

Instructions

One-paragraph 'what's going on with my portfolio right now' briefing — composed from existing tools, not new on-chain reads. Section coverage: (1) current portfolio total + window USD/% delta, (2) top 3 movers by absolute USD change across all chains, (3) Aave health-factor alerts (any HF < 1.5 surfaced with capitalized prefix and margin-to-liquidation %), (4) recent activity counts split into received / sent / swapped / supplied / borrowed / repaid / withdrew / other (action-type classification via 4byte-resolved methodName when present, directional fallback otherwise). Period: 24h (default — the morning-coffee briefing) / 7d / 30d. Address args mirror get_portfolio_diff (wallet / tronAddress / solanaAddress / bitcoinAddress — at least one required). Returns BOTH a structured envelope AND a pre-rendered markdown narrative (control via format). Sub-tool failures degrade to per-section notes rather than aborting (e.g. a Solana RPC outage doesn't void the EVM briefing). Two sections punted at v1 with explicit available: false reasons rather than silent omission: bestStablecoinYield (depends on the unshipped compare_yields tool) and liquidationCalendar (depends on the unshipped schedule_tx tool). Distinct from get_portfolio_summary (current state only) and get_portfolio_diff (window decomposition only) — this tool is the conversational AI rollup that sits on top of both.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
walletNoEVM wallet (Ethereum / Arbitrum / Polygon / Base / Optimism). Drives the EVM portion of every section: portfolio total, asset movers, Aave health-factor alert, recent activity counts.
tronAddressNoTRON mainnet base58 address. Folds TRX + TRC-20 totals + history into the briefing.
solanaAddressNoSolana mainnet base58 pubkey. Folds SOL + SPL totals + history into the briefing.
bitcoinAddressNoBitcoin address (any type). Folds BTC balance into the briefing. Bitcoin tx-history-derived activity counts are best-effort (indexer caps may truncate).
periodNoBriefing window. "24h" is the canonical morning-coffee briefing; "7d" / "30d" extend to weekly / monthly summaries. Pre-rendered narrative voice tightens for shorter windows.24h
formatNo"structured" returns the JSON envelope only. "narrative" returns only the pre-rendered string. "both" (default) returns both — agents typically use the narrative for verbatim relay and the structured for follow-up questions.both
Behavior5/5

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

The description adds significant behavioral context beyond annotations: it is composed from existing tools (not new on-chain reads), returns both structured and narrative formats, handles sub-tool failures gracefully, and explicitly lists missing features. 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.

Conciseness5/5

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

The description is dense but every sentence provides necessary information. It front-loads the core purpose and efficiently covers sections, parameters, and limitations.

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?

Given no output schema and the tool's complexity, the description fully explains the return format (structured envelope and narrative), sections, failure mode, and punted features. It is comprehensive.

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?

With 100% schema coverage, the description adds value by explaining address args mirror get_portfolio_diff, period defaults, and format options for agents. It enriches the meaning beyond the schema alone.

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 generates a one-paragraph portfolio briefing composed from existing tools. It distinguishes itself from sibling tools get_portfolio_summary and get_portfolio_diff by specifying it is a conversational rollup.

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?

The description explicitly defines when to use this tool: for a quick 'what's going on' briefing, defaulting to 24h. It also notes what is not covered (two punted sections with available: false) and differentiates from siblings.

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/szhygulin/recon-crypto-mcp'

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