Give your agent the whole job.
Choose the result you want. Make an agent-ready plan, run the supported preparation and carry the remaining steps into your own tools.
1. Choose & configure
Set your target, location or task inputs.
2. Prepare & inspect
Run public reads, keep their actual results.
3. Continue with your agent
Take the plan, handoffs and checks with you.
Plan a remote telescope night and return an image
An agent handoff plan from target selection through provider booking, permitted frame downloads and local image processing. No telescope booking runs through this gateway.
For An amateur astronomer, maker or researcher using their own browser-capable agent and telescope-provider account.
The path to your result
- 01
Draft the target and acquisition plan
Your agent
Your agent uses a suitable installed astronomy planner and current instrument documentation. Derive settings from the actual target and available instrument; do not treat a suggested exposure as a provider-supported setting. For StellarDock, current provider documentation describes a New Plan with target lookup, framing, altitude information and exposure settings; verify these in your actual session. Saving a plan does not book telescope time.
What counts as finished
- Record target, desired date/timezone, site requirements, candidate filters and exposure/count assumptions.
- Mark unresolved target, instrument or acquisition requirements.
- 02
Check site weather, Moon and target visibility
Your agent
Use your own astronomy planner and site-appropriate weather sources. This workflow has no native target-visibility or Moon-separation tool. A general forecast alone does not prove suitability.
After: target-plan
What counts as finished
- Record candidate site, observing window, target visibility and Moon conditions with sources and times.
- Identify missing weather or visibility checks before booking.
- 03
Inspect provider access and obtain an exact quote
Your provider / browser
Use the chosen provider directly through an authorized browser session or supported provider connection. Do not bypass login or access controls. StellarDock is listed here as browser access, not an executable gateway booking tool. Verify current provider capabilities and permitted automation before relying on them.
After: conditions
What counts as finished
- Confirm current account access, compatible instrument and available session through the provider.
- Show the exact proposed session, total cost, currency and relevant terms to the user.
- 04
Book only the explicitly approved session
Your provider / browser
This is a handoff to the user or their authorized browser agent, not server execution. The supplied budget and workflow request do not authorize a purchase. Avoid duplicate bookings on retries. StellarDock documentation distinguishes Save Plan from reservation or Run Now; reservation/Run Now charges credits upfront. Never treat Save Plan as a booking receipt.
After: provider-readiness
What counts as finished
- Obtain explicit authorization for the exact session and total before any booking or payment.
- Record the booking identifier and independently read back provider confirmation; stop if the quote or session changes.
- 05
Retrieve permitted acquisition files
Your provider / browser
Read the provider session result before downloading. Do not claim acquisition succeeded from a booking receipt alone, and do not promise a file format or calibration product until the provider confirms it. StellarDock documentation directs completed-session users to My Data → Download Data and describes optional calibration frames/JPEG previews. It notes browser FITS decompression and unsupported downloads on Safari/iPhone/iPad; verify your download environment.
After: booking
What counts as finished
- Confirm the session actually produced files and retain acquisition metadata.
- Download files only where the provider permits, to the user-approved local directory.
- Record a manifest of the files actually obtained; missing data remains incomplete.
- 06
Calibrate and stack locally when supported
Your local tools
Your local agent may inspect and process the acquired files with suitable installed tools. Do not invent calibration frames or claim calibration/stacking occurred before actual execution. Ask for missing installation or processing authorization where needed. StellarDock states it acquires and delivers images rather than performing stacking, calibration or processing; the local processing stage is separate.
After: download
What counts as finished
- Identify installed processing tools and the calibration inputs actually available.
- Record commands or settings and the produced image path.
- Preserve originals and disclose omitted or unsupported processing.
- 07
Return the image with its provenance
Your agent
Completion requires real acquisition files and an actual image artifact. A plan, screenshot, booking draft or provider link is not a completed observing run.
After: process
What counts as finished
- Return the actual produced image and file manifest.
- Include target, site/instrument, exposure metadata, booking/session reference and processing record when available.
- Distinguish user-reported claims from independently inspected provider and file evidence.
The intended result: A handoff plan for the user’s own agent. The desired eventual result is a real acquired image with source files and provenance; the gateway does not execute or verify that telescope outcome.
Access, coverage and limits
- Inspired by user-supplied screenshots of a reported Claude remote-telescope workflow. The historical account and its execution have not been independently verified.
- Provider capabilities, availability, automation permission and account access require current verification; screenshots do not establish them.
- No provider credentials, payment details or browser session secrets belong in workflow inputs.
- This workflow does not schedule recurring observing, book telescope time, download files or run local processing on the server.
- The example has budget 0 and account_available false: it grants no spend or account access and cannot be treated as a booking-ready request.
Remote telescope access guide · StellarDock listing
Provider documentation: StellarDock: Take your first image · StellarDock: Image downloads and refunds · StellarDock: What we support
Use this with your own agent
Connect to Real World MCP. Ask your agent to discover with search_workflows, inspect get_workflow, then use run_workflow for the supported preparation. Copying a plan does not run it.
{
"name": "run_workflow",
"arguments": {
"workflow_id": "remote-telescope-night",
"input": {
"target": "M42",
"observing_date": "Choose a date and timezone",
"provider": "StellarDock",
"account_available": false,
"budget": 0,
"currency": "USD",
"output_directory": "./telescope-output"
}
}
}Copy agent plan includes your edited inputs, every handoff and the completion checks.
Preparation results
Full run response
Prepare a coastal outing briefing
Combine local weather periods, active alerts and nearby tide predictions into a source-backed briefing.
For A coastal visitor, paddler or household planner researching an outing.
The path to your result
- 01
Get the local weather forecast
Runs here · public data
nws.forecastWhat counts as finished
- Return forecast periods with their source and time context.
- 02
Check active weather alerts
Runs here · public data
nws.alertsWhat counts as finished
- Return active alerts or an explicit empty result; preserve source context.
- 03
Find nearby predicted tides
Runs here · public data
noaa_tides.tides_nearWhat counts as finished
- Identify the station, its distance, datum and time reference when available.
- Return tide predictions or an explicit station-coverage failure.
The intended result: A combined result containing the three source responses and their individual execution states; check timestamps, alert instructions and station coverage before making plans.
Access, coverage and limits
- NWS weather coverage is limited to supported U.S. locations and territories.
- NOAA tide stations do not cover every coast; station distance and local conditions matter.
- Predictions and alerts do not establish safe swimming, boating or access. An empty alert result does not mean no hazard.
Use this with your own agent
Connect to Real World MCP. Ask your agent to discover with search_workflows, inspect get_workflow, then use run_workflow for the supported preparation. Copying a plan does not run it.
{
"name": "run_workflow",
"arguments": {
"workflow_id": "coastal-briefing",
"input": {
"lat": 37.8,
"lon": -122.47
}
}
}Copy agent plan includes your edited inputs, every handoff and the completion checks.
Preparation results
Full run response
Prepare an aurora photography briefing
Read NOAA aurora model estimates and a U.S. location forecast for one viewing spot.
For An amateur astronomer or photographer investigating an aurora outing.
The path to your result
- 01
Read the near-term aurora model
Runs here · public data
noaa_swpc.aurora_chanceWhat counts as finished
- Return observation and forecast times, overhead estimate and poleward context.
- 02
Read the viewing-location forecast
Runs here · public data
nws.forecastWhat counts as finished
- Return weather forecast periods or an explicit coverage error.
The intended result: A timestamped model-and-weather briefing, with each source response and any missing coverage visible.
Access, coverage and limits
- The aurora model and weather forecast use different forecast windows.
- NWS forecast coverage is limited to supported U.S. locations and territories even though aurora model lookup accepts global coordinates.
- General weather periods are not a cloud-cover, astronomical-darkness or access calculation. No sighting is guaranteed.
Use this with your own agent
Connect to Real World MCP. Ask your agent to discover with search_workflows, inspect get_workflow, then use run_workflow for the supported preparation. Copying a plan does not run it.
{
"name": "run_workflow",
"arguments": {
"workflow_id": "aurora-outing",
"input": {
"lat": 64.84,
"lon": -147.72
}
}
}Copy agent plan includes your edited inputs, every handoff and the completion checks.
Preparation results
Full run response
Find lower-carbon electricity forecast windows
Get GB carbon-intensity forecast periods for planning a flexible household task.
For A household planner comparing times for a flexible electricity task.
The path to your result
- 01
Read carbon-intensity forecast periods
Runs here · public data
carbon_intensity.forecastWhat counts as finished
- Return forecast slots and their intensity units.
- Preserve the provider result, including any lowest-intensity window it identifies.
The intended result: A source-backed forecast for comparing flexible electricity-use windows without operating any device.
Access, coverage and limits
- Great Britain coverage only.
- Carbon intensity is not electricity price, and a forecast does not guarantee actual emissions savings.
- The workflow does not operate appliances, set charging schedules or read a household tariff.
Use this with your own agent
Connect to Real World MCP. Ask your agent to discover with search_workflows, inspect get_workflow, then use run_workflow for the supported preparation. Copying a plan does not run it.
{
"name": "run_workflow",
"arguments": {
"workflow_id": "electricity-window",
"input": {
"postcode": "RG10",
"hours": 12
}
}
}Copy agent plan includes your edited inputs, every handoff and the completion checks.
Preparation results
Full run response
These are proposed workflows. Run results report only the steps actually executed. Provider and local handoffs need your own agent, access and authorization.