The valuable part is not asking an agent for a prettier summary. It is giving the agent a repeatable sequence that checks data freshness, fixes definitions, compares like with like, and names uncertainty before publishing a conclusion.
The first tool call should check sync status. If one provider failed yesterday, a portfolio decline may be missing data rather than lost revenue. The agent should surface stale projects and stop short of a confident ranking until the gap is understood.
Next, define the period, timezone, and currency. Never blend USD and EUR into one total without an explicit conversion source and timestamp.
Gross sales, net revenue, and MRR answer different questions. A good agent states which metric it is using and does not infer subscription MRR from a stream of one-off revenue events.
Ask for both the absolute change and percentage change. A tiny product can grow 200% on a small base; a mature product can add more money at a lower percentage.
A repeatable prompt reduces narrative drift and makes month-to-month reports comparable. Give the agent explicit stop conditions when data is stale or currencies are incompatible.
Check sync health first. If any project is stale, name it and qualify the analysis.
Compare net revenue by project for this month versus the same elapsed days last month.
Keep currencies separate. Show absolute and percentage changes.
Use recent events only to explain observed changes; do not invent causes.
Finish with three actions and cite the period, currency, and project behind each.An analyst does not need the ability to refund payments, cancel subscriptions, or edit customers. A read-only MCP surface limits the blast radius of a bad prompt and makes unattended scheduled reporting easier to approve.
If you also connect an official provider MCP with write tools, separate the workflows. Use VerifiedMRR for analysis, require human approval for provider-side actions, and never let a narrative conclusion automatically trigger a money-moving command.
Data freshness and sync status. A stale import can look like a revenue decline and invalidate every conclusion that follows.
Not by default. Keep currencies separate unless you provide an explicit exchange-rate source, conversion timestamp, and reporting-currency policy.
Revenue analysis needs observation, not payment operations. Read-only tools reduce risk and keep report generation separate from refunds, subscription changes, and payouts.
Connect a read-only revenue source and let the agent analyze current, scoped portfolio data.