1. Connect the NexusTrade app your dot will use
Open Plugins in ChatGPT, inspect the NexusTrade plugin if it is listed, and connect its included app through NexusTrade OAuth. On mobile, your dot's profile → Customize → Plugins opens shared settings. Your dot uses the connected account's enabled plugins and allowed actions.
For a private remote MCP connection, eligible ChatGPT web accounts use Settings → Apps → Advanced Settings → developer mode, then Settings → Apps → Create (or an administrator's Workspace settings → Apps → Create). Name it NexusTrade, choose OAuth, enter the URL below, select Scan Tools, finish sign-in and select Create. Full action access depends on the plan, workspace role and administrator settings; read/fetch access alone cannot submit a backtest or deploy a paper book.
Install Plugin Creator, mention @plugin-creator in a chat and ask it to include the connected NexusTrade app in a private research plugin. Review the app and instructions, finish creation and install it. In your dot, select that plugin for this task and perform the read check below. A plugin containing only instructions has no account tools.
NexusTrade MCP URL: https://nexustrade.io/api/mcp
Authentication: OAuth
Include the connected NexusTrade app, then verify owned portfolio reads before enabling actions.2. Check the account with an owned portfolio read
Ask the agent to call fetch_portfolios with the arguments below. Compare the returned portfolio names, IDs and types with your NexusTrade account. fetch_portfolios returns portfolioId; pass that exact value as portfolio_id to get_portfolio. Inspect the structured portfolio.portfolioId, portfolio.type, portfolio.isActive, portfolio.strategies, portfolio.initialValue and portfolio.deployment. For a new account, an authenticated empty list is a valid result. Public stock commentary does not establish account access.
This request excludes live books and positions, includes chat drafts and inactive paper books, and returns up to 50 records per page. Follow subsequent pages before concluding a named book is absent. If OAuth expired, reconnect and repeat this read. For a missing tool, inspect the included app, environment and action permissions. An account mismatch must be fixed before a write.
{
"include_live": false,
"include_paper": true,
"include_chat_portfolios": true,
"include_inactive": true,
"include_positions": false,
"limit": 50,
"page": 1
}3. Start the AMD memo with reported facts
AMD published Q2 2026 results on August 4 for the quarter ended June 27. GAAP revenue was $11,536 million versus $7,685 million a year earlier; AMD reported 50% growth. GAAP gross margin was 54%. Keep the reported unit as millions rather than silently treating the table as billions.
The release says the comparable 2025 quarter included an $800 million inventory and related charge caused by export controls. That affects interpretation of the margin comparison. Your memo can infer that the current revenue base grew, but it needs separate evidence for repeat orders, customer concentration and cash conversion. Record later guidance changes as dated updates and keep this reported quarter intact.
| Issuer and ticker | Advanced Micro Devices · AMD |
| Reporting period | Q2 ended June 27, 2026 |
| Published | August 4, 2026 |
| GAAP revenue | $11,536 million; prior year $7,685 million |
| Reported revenue growth | 50% year over year |
| Comparison caveat | Prior-year $800 million export-control inventory and related charge |
No matching rows. Clear the filter to see all records.
4. Read the filing list before starting paid research
Use sec_edgar to list AMD filings with the read-only request below. Open the relevant 10-Q and earnings 8-K; confirm issuer, accession, reporting period and filed date. The example above is a dated source check, not a claim that it will remain the latest quarter.
Missing filing values stay unresolved. action=ingest_filings persists source text and is a separate write, so listing filings does not grant permission to ingest them.
{
"ticker": "AMD",
"action": "list_filings",
"forms": [
"10-Q",
"8-K"
],
"since": "2026-07-01",
"limit": 10
}Read the reported quarterly fundamentals
Use this separate sec_edgar request to read available quarterly XBRL metrics. Match each observation to its fiscal period, unit and filing date rather than assuming the first row is the quarter in this example. Open the issuer statement to resolve any discrepancy. A missing operating cash-flow value remains missing.
{
"ticker": "AMD",
"action": "fundamentals",
"periods": "quarterly"
}5. Submit one bounded question, then poll its ID
After reviewing the question and its usage cost, explicitly approve one research_topic call with message. The structured result returns researchJobId and status. Copy that returned ID into get_research_status as research_job_id. PROCESSING means poll the same job; COMPLETED should include the report and citations; FAILED includes an error to inspect.
If the response is lost, inspect the task transcript for the accepted ID before starting another request. A second research_topic call can create another billed job. A missing or foreign ID is an ownership or identity problem, not an instruction to invent a result. Read each primary citation before accepting the brief.
After I approve one research_topic request, use message: "Research AMD using the primary earnings release and corresponding 10-Q. Compare reported revenue and operating cash flow with the matching prior-year period. Preserve GAAP basis, units, quarter-end and publication dates. Explain disclosed one-off items, customer concentration and missing evidence. Return facts, interpretation and disconfirming evidence with source URLs. Do not draft orders or alter portfolios."
Save the returned researchJobId. Call get_research_status with research_job_id set to that exact value until terminal status.From a question to evidence
research_topic is asynchronous. Poll get_research_status with the same job ID instead of launching another billed research run for the same question.
| Read filings | sec_edgar | Issuer, accession, reporting period and publication date |
| Read relevant news | search_stock_news | Dated publisher links; distinguish news from filings |
| Submit bounded research | research_topic | researchJobId and source-backed question |
| Poll the accepted job | get_research_status | Same research_job_id, completed report and citations |
No matching rows. Clear the filter to see all records.
6. Keep an AMD memo current without repeating the research job
Save the brief as AMD research memo with the source date, the accepted researchJobId and open questions. Ask your dot for one weekly check through November 6, 2026, Friday at 4:30 p.m. America/New_York. It should read new issuer publications and update the memo only when a fact changes; another paid research job still needs separate approval.
In profile → Customize → Custom rules, save Ask before taking action for paid research, strategy edits and deployment. Ask the dot to confirm the exact schedule and end date, then review it under Scheduled. Check the first task's output in Activity: a completed task should have a dated source diff, not simply an assertion that nothing changed. Pause the dot's work and cancel the saved schedule separately when ending the assignment.
Maintain my AMD research memo. Once each Friday at 4:30 p.m. America/New_York through November 6, 2026, check AMD investor relations and SEC filings. Record newly published links and which facts changed. Reuse the saved brief; do not resubmit research_topic for the same question. Notify me only for a new filing, revised guidance, a material contradiction or a connection failure. Ask before a new paid job, portfolio edit or deployment. Confirm the saved schedule and end date.Choose a separate strategy experiment
A filing brief ends with a documented thesis and what would change it. Turning that thesis into a rule requires a separate entry, exit, sizing and timing decision. The price-rule guide below tests mechanics; it does not retrospectively treat a 2026 earnings release as information known in 2021.