Short answer
Here are real examples of an MCP server in use, from Fieldproxy's field service MCP server: each shows the request a person types into Claude, ChatGPT or Copilot, the tool the assistant calls, and the result. They cover reading data, dispatch, messaging, documents, photos and changing the software itself.
Examples by area
| Request | Tool the AI calls | Result |
|---|---|---|
| Give me today's operations briefing | daily_ops_briefing (workflow) | Late, unassigned and overdue work |
| Which jobs finished last month have no invoice? | unbilled_completed_jobs | Every unbilled job and its value |
| Who is overdue more than 60 days? | ar_aging | AR ageing by customer |
| Mike is out sick, move his jobs | plan_job_distribution, apply_schedule | A proposed re-plan, applied on confirm |
| Plan tomorrow's routes for the North region | plan_day_routes | Routes with drive time |
| Who is nearest the Westfield site? | nearest_technicians | Technicians ranked by distance |
| Draft reminders for these customers | draft_email, confirm_send | Drafts, sent after you confirm |
| Issue the proposal for Site 14 | preview_proposal, issue_proposal | A proposal from your template |
| Show me the before and after photos on job 4471 | view_images | The photos, compared |
| Why did last night's automation fail? | why_did_this_automation_fail (workflow) | The failed run and the cause |
| Add a warranty expiry date to every job | add_column, validate_app | A new field, as a sandbox draft |
| Email me 30 days before a warranty expires | save_automation | An automation, saved switched off |
What every example has in common
Reads return immediately. Anything that changes data, sends a message or builds is a proposal first: the assistant shows it, a person confirms, and writes can be undone.
Fieldproxy facts on this page come from the Fieldproxy MCP reference. Competitor details are from each vendor's own documentation as of September 27, 2026; see the comparison table and sources.