DEV Community: Tejal Laxkar

Read freely, confirm every change: MCP tools for golf cart fleets

Tejal Laxkar — Thu, 29 Oct 2026 15:15:03 +0000

Split a golf cart fleet's MCP tools into two groups. Read tools (battery, location, faults, zone breaches, trips) answer questions and can run freely within a person's permissions. Action tools (create a work order, lock, unlock, restart) never act on their own; they return a proposal, and a person confirms it in the AI app. Scope every call to the signed-in person, refuse vehicle commands during an active trip, mask rider personal data by role, and log everything.

That is the whole design. The rest is how to build it: two illustrative JSON shapes, a guardrail table and a pre-launch checklist.

Why split fleet MCP tools into read and action tools?

Because the failure modes differ. A bad read gives a wrong answer a person can check against the console. A bad action locks a cart with a guest on it, restarts a device mid-ride, or opens a work order on someone else's vehicle.

The MCP specification puts it plainly: "For trust & safety and security, there SHOULD always be a human in the loop with the ability to deny tool invocations." It also says applications SHOULD "Present confirmation prompts to the user for operations". Source: MCP specification, Tools.

Treat every tool the same and you either prompt on every "Which vehicles are low on battery before Saturday's rentals?" or you let a model lock carts. Two classes, two rule sets.

What does a read tool look like?

A read tool takes a scope plus filters, returns facts, and is annotated read-only. Discovery happens through tools/list, calls through tools/call. An illustrative shape, not any product's real tool:

{
  "name": "list_low_battery_vehicles",
  "title": "List low-battery vehicles",
  "description": "Returns vehicles in one fleet whose latest battery reading is at or below a threshold. Read-only.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "fleet_id": {
        "type": "string",
        "description": "A fleet the signed-in person can access"
      },
      "battery_percent_max": {
        "type": "integer",
        "minimum": 0,
        "maximum": 100,
        "default": 30
      },
      "booked_before": {
        "type": "string",
        "format": "date-time",
        "description": "Optional. Only vehicles with a rental starting before this time"
      }
    },
    "required": ["fleet_id"]
  },
  "annotations": {
    "readOnlyHint": true,
    "destructiveHint": false
  }
}

Three things to notice. fleet_id is required, and the server checks the signed-in person can access that fleet instead of trusting the argument. The threshold has bounds in the schema, and the server validates again on every call, because the spec says servers MUST validate all tool inputs. The annotation tells the client this tool is safe to run without a prompt, but clients MUST treat annotations as untrusted unless they come from a trusted server, so it is a UI hint, not a security boundary.

Other reads worth building: vehicles that left a zone or entered an off-limits area in a date range (zones warn the rider and record the breach; they do not touch the cart), carts whose health score dropped this week, open faults, trips per cart, carts that moved while locked, vehicles due for service.

Why should action tools return a proposal instead of acting?

Because the model is drafting, not deciding. An action tool validates the request, runs the same checks the console would run, and returns a proposal the client can show the person. Nothing changes until a second call carries that person's confirmation. Again an illustrative shape, not any product's real tool:

{
  "status": "proposed",
  "proposal_id": "prop_8f3a21",
  "action": "lock_vehicle",
  "vehicle_id": "veh_0142",
  "requested_by": "user_77",
  "checks": {
    "role_may_lock": true,
    "vehicle_in_workspace": true,
    "active_trip": false
  },
  "expires_at": "2026-10-29T14:35:00Z",
  "message": "Lock cart 142? Nothing happens until you confirm."
}

The AI app renders this as a confirmation prompt. On yes, the client calls a separate confirm_proposal tool with the proposal_id. If the proposal has expired, or the checks no longer pass because a trip started in the meantime, the confirmation fails and the person is told why. There is no path from "lock cart 142" to a locked cart without a human decision, and the propose and confirm steps are the only two places state changes, so they are the only two places you have to harden.

How do you scope permissions per person and role?

Give the AI app the same view the person has in the console, nothing more, and no shared service account. Each session is tied to one human login, so tools/list returns only the tools that role may use and every tools/call is filtered to that person's workspace. Three scopes matter:

Workspace. A dealer supporting several customer fleets sees only the fleet they are signed into.
Role. A mechanic can propose work orders; a front desk role may read battery and location but cannot propose a restart.
Money. If a role cannot see revenue in the console, money tools return nothing in the AI app. Not zeros, not a "restricted" placeholder, nothing, because a model reasons over whatever it is handed.

When should the server refuse a command outright?

Some refusals belong above the confirmation step, because no one should be able to confirm them from a chat window. The clearest for carts: refuse lock, unlock and restart while a rider is on an active trip. A locked cart on a fairway is a stranded guest. Add refusals for a vehicle outside the person's workspace and for bulk commands when the role may act on one vehicle at a time.

How do you mask rider data by role?

Trips and riders are the most useful reads and the most sensitive. Mask at the server, per field, per role. A role that cannot see rider names, emails and phones in the console gets the same fields masked in every response: the trip, cart, times and route stay visible; identity fields come back as masked tokens. Do it before serialization so no tool can leak a raw field by accident, and sanitize free text (support notes, damage descriptions) the same way, since the spec requires servers to sanitize tool outputs.

What should the audit log record?

The spec says clients SHOULD log tool usage. Log on the server too, since you hold the facts. For each call, record the human account (not the AI app), the tool, the validated inputs, the resolved workspace and the result size. For actions, add the proposal id, the checks run, who confirmed, when, and the command outcome. Rate limit per person and per tool so a looping client cannot hammer reads or flood the console with proposals.

The whole model in one table:

Tool type	Examples	What the AI app may do	Guardrail
Read: vehicle state	Battery, location, health score, open faults	Query and summarize freely	Scoped to the person's workspace and role
Read: activity	Trips, zone breaches, locked-cart movement, ride replays	Query and summarize freely	Rider identity fields masked by role
Read: money	Revenue, receipts, pass sales	Query only if the role sees revenue in the console	Nothing returned to other roles
Action: maintenance	Create or close a work order	Propose only	Person confirms; proposal id logged
Action: vehicle command	Lock, unlock, restart	Propose only	Refused during an active trip; person confirms

What should you check before you expose a fleet to an AI app?

List every tool and label it read or action. Nothing in between.
Check each action tool returns a proposal and has no code path that executes on its own.
Tie each session to one human account. No shared tokens for AI apps.
Mirror console permissions exactly: workspace, role, revenue visibility.
Mask rider names, emails and phones for roles that cannot see them in the console.
Add hard refusals no confirmation can override, starting with commands during an active trip.
Validate every input on the server and drop fields the model invents.
Rate limit per person and per tool.
Log every tools/call, proposal and confirmation with who, what, when and result.
Test with the least privileged role first, then with prompts designed to talk the model into escalating.

What does this look like in practice?

At Axons Mobility we built this pattern into the Axons Mobility MCP server. It exposes 40+ tools across vehicles and devices, trips and riders, money, repairs and support, pricing and zones, and insights and reports. Each person gets only their own permissions, matching the console: their workspace, what their role allows, masked rider names, emails and phones for roles that cannot see them, and no revenue in the AI app for anyone who cannot see it in the console.

The AI app can propose a work order or a lock, unlock or restart command, but nothing happens until a person confirms, and vehicle commands are refused while a rider is on a trip. To try the pattern on a fleet: copy your MCP address from the console, add it as a connector in Claude, ChatGPT or another MCP app, sign in with your own Axons Mobility account, approve the connection, and ask which vehicles are due for service.

Golf Cart Theft Prevention for Resorts: Tracking, Alerts and a 2 a.m. Plan

Tejal Laxkar — Wed, 28 Oct 2026 14:03:34 +0000

Most resort carts are not stolen by experts. They are taken because nobody notices until breakfast.

A resort cart rarely disappears in a dramatic way. A guest keeps it overnight. A staff key gets copied. A cart parked by the beach path is driven off after the bar closes. The pattern is the same each time: the cart is found missing the next morning, hours after anything could be done.

So good theft prevention for a resort is less about locks and more about time. The faster you know, the cheaper the problem.

Three layers that work together

1. Lock the cart when it is not rented. Keyless carts that unlock only from the rider app or a staff key card remove the shared-key problem. No key left in the cart means no casual joyride.

2. Alert the moment a locked cart moves. This is the layer that changes outcomes. If a parked, locked cart starts rolling at 2 a.m., the night manager gets an alert with its position, not a report the next day.

3. Track it on a live map. With GPS tracking, security can see where the cart is heading and meet it, often before it leaves the property. A zone around the resort edge records any cart that crosses it.

What resort teams should set up first

Who gets the alert at night, and how they are reached.
Which hours count as "after hours" for each group of carts.
Where the property edge is, drawn once as a zone.
A simple rule for guests who keep a cart past checkout.

Tracker only, or something more?

A basic tracker hidden under the seat tells you where a cart is if someone remembers to check. For a resort with dozens of carts, the alert is what matters, because nobody watches a map all night. Look for tools that tie the lock, the movement alert and the map together, and that work on the carts you already have.

The real goal

The best result is not a recovered cart. It is a cart that never left. When staff know within a minute, most incidents end with a polite word at the gate.

For a closer look at how this works, see golf cart theft alerts and GPS tracking for resorts and how it fits into resort golf cart rental.

Golf Cart GPS Tracking Compared: 4 Options for Rental Fleets, Resorts and Dealers

Tejal Laxkar — Sun, 18 Oct 2026 17:51:33 +0000

Golf cart GPS tracking can be added to almost any golf cart or LSV: a GPS device goes on the cart, and software turns its location data into alerts, zones and reports. The real choice is what you need on top of the dot on the map, whether that is a simple tracker, a golf course system, or rental software that works with the devices already on your carts.

The question matters more each season. Golf Inc.'s September/October 2026 issue ran a feature on "the connected golf course," arguing that cart GPS data pays off most when it is linked with the rest of the operation (Golf Inc.). This guide compares four real options on the points buyers ask about. Every fact about another product comes from that product's own website (see Sources).

Can I add GPS tracking to any golf cart or LSV?

Usually, yes. Battery trackers mount without wiring, and fleet systems use hidden sensors or screens. Before you choose, check three things: does it work with every cart brand in your fleet, what happens when a cart leaves the property, and who will act on the data.

What should I compare?

Who it is built for
Hardware: your own devices, or theirs
Zones and alerts
Guest or rider app
AI features, and MCP (asking Claude or ChatGPT about the fleet)
Pricing model and free trial
Integrations

How do the four options compare?

	Axons Mobility	Hapn	FAIRWAYiQ	LandAirSea 54
Built for	Golf cart rental operators, dealers and OEMs	Golf cart rental and resort fleets	Golf course operators	One cart or a whole fleet
Hardware	Works with the devices already on your vehicles, any maker	Battery GPS tracker, hidden mount, no wiring	Cart screens or hidden GPS sensors, all cart brands	Magnetic battery GPS tracker, hard-wired option
Zones and alerts	Zones warn guests who leave; alert when a locked cart moves	Geofence exit alerts; tamper alerts	Turf protection and geofencing	Safe-zone and unauthorized-movement alerts
Extra features	Branded rider app, keyless unlock, Intelligence health scores, MCP for Claude and ChatGPT	Utilization and idle-cart reports; open API	Pace of play; cart screen with course map	Updates as often as every 3 seconds, by plan; route history; app and web portal
Pricing model	Paid monthly plan, 15-day free trial	Per cart, hardware plan or month to month	Per cart per month, in tiers	Monthly subscription

Which option fits which fleet?

If you mainly need to know where carts are, and get an alert when one leaves, a tracker such as Hapn or LandAirSea covers that.
If you run a golf course and care most about pace of play and turf, FAIRWAYiQ is built for that job.
If you rent carts to guests or residents, and want GPS data to drive unlocks, zones, pricing, payments and repairs, rental software such as Axons Mobility sits on top of the devices you already have.

What does Axons Mobility add on top of GPS?

The branded dashboard shows a live map of every cart, plus riders, pricing, repairs and accounting. Ride Replay redraws any trip street by street with time and speed, with hard braking, potholes and zone breaches marked. Riders pay into your own Stripe account, and a weekly written summary explains why revenue moved.

That is the step from golf cart GPS tracking to a fleet you can run. See how it works for golf cart rentals.

Sources

Hapn, golf cart fleet tracking: gethapn.com/equipment-rental/golf-cart
FAIRWAYiQ: fairwayiq.com and fairwayiq.com/llms.txt
LandAirSea, golf cart GPS tracker: landairsea.com/pages/golf-cart-gps-tracker
Golf Inc., "The connected golf course," September/October 2026: Golf Inc.
Axons Mobility: axonsmobility.com

Golf Cart Dealer Software: Add Rentals and Fleet Services as a New Revenue Line

Tejal Laxkar — Sat, 17 Oct 2026 18:34:41 +0000

Golf cart dealer software should do more than track stock and service tickets: it should let a dealer run golf cart rentals from booking to return. Axons Mobility does this with a branded rider app, keyless unlock, a live operator dashboard and Intelligence that tells you what to do next, all on the devices already on your carts.

Why are golf cart dealers looking at rentals and fleet services?

Dealers already have what a rental business needs most: carts, a service bay and local customers. Resorts, holiday parks, beach towns, campuses and gated communities want carts for guests and residents, and many of them would rather have someone else run the fleet.

Fleet deals can be large. In October 2026, a public golf course in Portland, Oregon invited bids to lease 115 new electric golf carts, plus a beverage cart and a range picker, for three to five years from March 2027 (bid notice in The Outlook). Deals like this are a chance to offer more than the carts: rentals for guests, and fleet services on top.

What does a dealer need to run golf cart rentals from booking to return?

A guest app, a way to unlock carts without handing out keys, rules for where carts can go, pricing, payments, and one place to see the whole fleet. In Axons Mobility, that means:

A branded rider app for iOS and Android, in 8 supported languages, built and published under your brand
Keyless unlock by app or NFC key card, so there are no keys at the front desk
Zones that warn guests when they leave the property, and log every crossing
Hourly pricing with a per-ride cap, day passes and promo codes
Payments that go into your own Stripe account
An ID check before the first ride, and the nearest parking zone shown before a ride ends

Do I need new hardware on the carts?

No. Axons Mobility works with the devices already on your vehicles, from any maker. It shows the right battery level for 48 V carts, and it sends an alert when a locked cart moves.

How do I keep the carts healthy and earning?

This is where Intelligence helps. Every cart gets a health score, and alerts become work orders for your service team. Revenue ideas come with an estimated weekly gain, so you can see which change is worth making first. Intelligence also shows riders who are at risk of leaving, so you can win them back early. Intelligence is free up to 25 vehicles.

For a dealer, that means service work you can plan, not surprises at the busiest hour.

The branded dashboard also gives you a live map, riders, pricing, repairs and accounting in one place, plus a weekly written summary of why revenue moved. Ride Replay redraws any trip street by street with time and speed, with hard braking, potholes and zone breaches marked.

Can I ask Claude or ChatGPT about my rental fleet?

Yes. With MCP, you can ask Claude, ChatGPT or any MCP app questions like "Which carts need service before the weekend?" There are 40+ tools for vehicles, trips, riders, money and repairs. Each person sees only what their role allows, and nothing changes until a person confirms it. Inside the dashboard, the AI Assistant answers with a chart, a table or a link.

How does pricing work?

Axons Mobility is a paid monthly plan, with a 15-day free trial on your own vehicles, and you can cancel any time. See pricing.

How do I start?

Pick one site to start with: a resort, park or community that already buys or leases carts from you.
Connect the carts and the devices already on them.
Set zones, prices and passes, and launch your branded rider app.
Watch Intelligence for a few weeks, then grow to the next site.

That is how golf cart dealer software can become a new revenue line. You can also start a free trial on your own carts.

How to Start a Golf Cart Rental Business: The Software Side, Step by Step

Tejal Laxkar — Tue, 13 Oct 2026 17:53:08 +0000

How do you start a golf cart rental business, and what software do you need? You need a place with steady demand, carts that meet local rules, insurance, and software that handles booking, payment, unlock, zones and repairs. This guide covers the software side, step by step, so a small team can set it up once and run it every day.

Why are dealers and resorts asking this now?

The second GolfCarting Expo & Dealer Summit brought golf cart OEMs, dealers and suppliers together in Charleston, South Carolina, from 1 to 3 October 2026. For dealers, resorts and communities that already own carts, rentals are a natural new revenue line. The hard part is rarely the carts. It is running rentals every day without a big front desk.

Step 1: Where will guests rent, and how will they ride?

Pick the setting first, because it decides the software you need:

Resorts and holiday parks: guests walk up, ride for an hour or a day, and stay on the property
Beach towns and islands: longer rides, often with street-legal carts or LSVs
Campuses and gated communities: residents or staff share carts every day

If guests walk up and ride, you need self-service: an app, keyless unlock and zones. If you deliver carts for a week, booking and delivery matter more.

Step 2: What should the guest experience look like?

Guests should go from sign-up to driving in a few minutes, with no keys at a desk. With Axons Mobility, the operator gets a branded iOS and Android rider app in 8 supported languages, built and published for them. Guests sign up, pass an ID check, add a card and unlock a cart with the app or an NFC key card. Scan to Ride, short holds and group rides are built in. Before the ride ends, the app shows the nearest parking zone. Riders pay into the operator's own Stripe account.

Step 3: How will you price rentals?

Start simple. Two models are easy to explain to guests: hourly pricing with a per-ride cap, or day passes for guests who stay longer. Axons Mobility supports pricing by time or distance, passes and promo codes, so you can test offers in your first season without changing systems.

Step 4: How will you protect the carts?

Carts leave the property, get parked in the wrong place, or move when they should not. Set this up before the first guest arrives:

Zones that warn guests who leave the property and log every crossing
An alert when a locked cart moves
Correct battery readings for 48 V carts
Ride Replay, which redraws a route street by street with time and speed, and marks hard braking, potholes and zone breaches

Ride Replay also helps you answer a damage question or a fare dispute with facts, in the app and in the dashboard.

Step 5: Do you need new hardware?

Not always. Axons Mobility works with the devices already on the carts, from any maker, so a dealer or resort with connected carts can start without buying new hardware. You see every cart on a live map in the branded dashboard.

Step 6: How will a small team keep up?

This is where AI helps most. Axons Mobility Intelligence gives every cart a health score. When a score drops, the alert becomes a work order, so the right person fixes the cart before a guest finds the problem. Intelligence also shows revenue ideas with an estimated weekly gain and riders at risk of leaving. It is free up to 25 vehicles, which suits a new fleet.

Through MCP, your team can ask Claude, ChatGPT or any MCP app questions like "Which carts need service before Saturday?" There are 40+ tools for vehicles, trips, riders, money and repairs. Each person sees only what their role allows, and nothing changes until a person confirms. Inside the dashboard, an AI Assistant answers with a chart, table or link, and a weekly written summary explains why revenue moved.

Step 7: How should you test it before launch?

Run a trial on your own carts, not a demo fleet. Check that guests can sign up and unlock in a few minutes, that a zone warning fires at the edge of the property, and that a cart health alert turns into a work order. Axons Mobility has a paid monthly plan with a 15-day free trial on your own vehicles, and you can cancel any time.

Where should you go next?

For the full list of features to compare, read our guide on how to start a golf cart rental business with the right software. To see how keyless unlock, zones and the branded rider app work together, visit the golf cart rental page.

Golf Cart Rental Software: How Keyless Rentals Work for Resorts and Beach Towns

Tejal Laxkar — Fri, 09 Oct 2026 22:26:14 +0000

Golf cart rental software lets guests unlock a cart with their phone or an NFC key card, so there are no keys to hand out, count or lose. The guest scans the cart in the operator's branded app, or taps a key card on the cart, and the ride starts.

This is a short summary of our full buyer's guide, which lists 12 features to check, a demo checklist and the questions to ask any vendor.

How do keyless golf cart rentals work?

The operator gives guests a branded iOS and Android rider app in 8 supported languages. Guests sign up, pass an ID check, and unlock a cart with the app or with an NFC key card. Before the ride ends, the app shows the nearest parking zone. Riders pay into the operator's own Stripe account.

What else should golf cart rental software do?

Unlocking is only the start. At a resort, beach town or gated community, the software also has to protect the carts and keep pricing simple:

Zones that warn guests who leave the property
An alert when a locked cart moves
Correct battery readings for 48 V carts
Hourly pricing with a per-ride cap, or day passes
Ride Replay, to see the route, speed and any zone breach after a ride

How does AI help a golf cart fleet?

Axons Mobility Intelligence gives every cart a health score. When a score drops, the alert becomes a work order, so the right person fixes the cart. Intelligence also suggests revenue ideas with an estimated weekly gain and shows riders at risk of leaving. It is free up to 25 vehicles.

Through MCP, your team can ask Claude, ChatGPT or any MCP app questions like "which carts need service before the weekend?". Each person sees only what their role allows, and nothing changes until a person confirms.

Do you need new hardware?

No. Axons Mobility works with the devices already on your carts, from any maker. You see every cart on a live map in the branded dashboard.

How can you try it?

Axons Mobility has a paid monthly plan with a 15-day free trial on your own vehicles, and you can cancel any time. See the golf cart rental software page, or start a free trial.

For all 12 features and the vendor questions, read the full guide: How to Choose Golf Cart Rental Software: 12 Features to Check.

Originally published at axonsmobility.com/blog/golf-cart-rental-software

Answers, Not More Dashboards: How Fleet Operators Can Decide What to Do Next

Tejal Laxkar — Tue, 06 Oct 2026 17:47:51 +0000

If you run a shared scooter, bike, moped or car fleet, or golf cart rentals at a resort or campus, you probably have lots of data. Trips, battery levels, rider sign-ups, payments, repairs. The problem is rarely a lack of numbers. The problem is time. Every morning someone opens several dashboards, compares charts and guesses what matters most today.

Dashboards show what happened. They do not tell you what to do next. That gap is where much of an operator's day goes.

The three questions every operator asks

Most daily decisions in a rental or sharing fleet come back to three questions:

Where can we make more money this week?
Which vehicles need attention before they break down?
Which riders are about to stop riding?

A good tool should answer these directly, in one place, without asking you to build a report first.

1. Revenue ideas with an estimated weekly gain

Pricing, passes, promo codes, zones: there are many levers you can pull. The hard part is knowing which one to try first.

Axons Mobility Intelligence looks at your own fleet data and suggests revenue ideas. Each idea comes with an estimated weekly gain, so you can compare them side by side and start with the one worth the most. Instead of "revenue is down, let's look into it", you get a short list of concrete changes to consider.

The operator console also sends a weekly written summary of why revenue moved. You read a few sentences instead of comparing two charts and guessing.

2. A health score for every vehicle

A breakdown costs you twice: once for the repair, and again for the rides you lose while the vehicle is off the street.

Intelligence gives every vehicle a health score. When a score drops, you get an alert, and that alert becomes a work order, so it lands with the person who will fix it. Your team does not need to watch battery charts all day. They see a list of vehicles that need care.

For golf cart fleets, this also covers practical details, like the correct battery level for 48 V carts and an alert when a locked cart moves.

3. Riders at risk of leaving

Keeping a rider you already have is usually easier than finding a new one. But many operators only notice a lost rider weeks after they stopped riding.

Intelligence flags riders at risk of leaving while there is still time to act. You can then reach them with tools already in the platform, such as a pass or a promo code, before they stop riding for good.

One view, not ten tabs

The goal is not more charts. The goal is one view that shows revenue ideas, vehicle health and riders at risk together, so the first minutes of your day are spent deciding, not searching.

For a follow-up question, the AI Assistant inside the console answers with a chart, a table or a link. If your team already uses Claude or ChatGPT, Axons Mobility also supports MCP, so they can ask about the fleet from those apps. Each person sees only what their role allows, and nothing changes until a person confirms.

Built for the fleet you already have

Intelligence is part of Axons Mobility, fleet software for scooter, bike, moped and car sharing, and for golf cart rentals in beach towns, islands, resorts, gated communities, campuses and holiday parks.

A few practical points:

No new hardware. It works with the devices already on your vehicles, from any maker.
Your own workspace. Each operator gets a private workspace, with role-based access and GDPR tools.
Free to start. Intelligence is free up to 25 vehicles.

A simple way to start

Pick the one question you spend the most time on today: revenue, vehicle health or riders leaving. Note how long it takes to answer it now. Then try the same question with Intelligence on your own vehicles.

Axons Mobility offers a 15-day free trial on your own vehicles. It is monthly, and you can cancel any time.

Fewer dashboards. More answers. That is how a fleet team gets its time back.