Skip to main content
Glama
evan-moon

firma

by evan-moon
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

get_brief

Get a synthesized portfolio brief that consolidates holdings, P&L, macro risks, news, earnings, and insights into a single narrative for market and portfolio questions.

Instructions

The single entry point for any market or portfolio question — call this first before reaching for individual tools. Bundles in one response: full holdings with weights and daily P&L; concentration (HHI by ticker/sector/country); today's movers; recent news per ticker; upcoming earnings; economic calendar; macro snapshot (VIX, 10Y yield, FX impact in home currency); Economic Stress Index (0-100); Macro Regime bias (Risk-on / Mixed / Risk-off from 5 signals); World Bank global macro (GDP growth, inflation, unemployment for major economies); active disaster alerts (GDACS Orange/Red); commodity prices (WTI, Gold, Copper); upcoming dividend calendar for holdings; and pre-computed insights that cross-reference all of the above with portfolio composition. Use this for: 'how is my portfolio doing', 'what's the market situation', 'brief me on this week / next week', 'what should I watch out for', 'any macro risks', 'any upcoming dividends'. Only call individual tools (show_macro / show_stress / show_regime / show_world_intel / show_valuation) when drilling deeper after reading the brief. Cached per day on disk. PRESENTATION RULE: Never list data sections sequentially. The response must be a synthesized narrative. Use insights[] as the primary thread — each entry already cross-references data sources. For each insight, explain the second-order consequence for the portfolio: a mover + upcoming earnings = compounding event risk; a regime shift + sector concentration = tail-risk amplifier; stress score + drawdown = whether to trim or hold. If the same ticker appears across movers, news, and earnings, that is the story — lead with it. Numbers are evidence, not the headline. The goal is one coherent read on what today means for this specific portfolio, not a structured report on what the data contains.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
refreshNoForce regenerate, bypass today's cache
home_currencyNoUser's home currency for FX context (USD/KRW/EUR/JPY/CNY/GBP). USD = no FX line.USD

Tool Definition Quality

A4.8/5.0
Behavior5/5

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

No annotations provided, but description fully compensates by detailing included data, caching behavior (per day on disk), and presentation rules. Clearly a read-only operation.

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

Conciseness4/5

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

Long but well-structured with purpose upfront. Some presentation rules are verbose but informative. Minor conciseness trade-off for completeness.

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?

No output schema, but description thoroughly explains response contents, caching, and usage context. Complete for agent decision-making.

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?

Schema coverage 100%, description adds context: 'force regenerate' for refresh and 'User's home currency for FX context' for home_currency. Adds meaning 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?

Description clearly states it is the single entry point for market/portfolio questions, distinguishes from individual tools by instructing to call this first before individual tools.

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 says 'call this first' and provides example queries. Instructs to only use sibling tools for deeper dives after reading the brief.

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/evan-moon/firma'

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