Skip to main content
Glama

Search Seat Sherpa carpools

search_rides
Read-onlyIdempotent

Find upcoming long-distance carpool rides on Seat Sherpa (California and Nevada) where everyday drivers sell the empty seats on a trip they are already taking, and riders split the cost of gas. Give a starting place and a destination as city or place names (for example "San Francisco" and "Los Angeles"), and optionally a travel date. Returns rides with open seats: route, departure date and time (Pacific), seats left, the all-in price per seat in USD (what the rider pays, fees included), the driver's first name, and a link where the person books. Rides that stop in a city count for that city, so a San Jose to San Diego ride with a Los Angeles stop is found for Los Angeles to San Diego. Booking happens on the link; this tool cannot book. Rides on a nearby route (for example a San Francisco ride for a San Jose search) are listed separately as nearby_rides; say they are nearby, not exact. When no ride fits exactly, the answer includes a link to post a ride request for that route (the same link request_ride_link gives).

Input Schema

NameRequiredDescriptionDefault
toYesWhere the rider is going, e.g. "Los Angeles", "Las Vegas".
dateNoOptional travel date, YYYY-MM-DD (Pacific). Today is 2026-11-03 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides.
fromYesWhere the rider starts: a city or place in California or Nevada, e.g. "San Francisco", "UC Davis", "Irvine".
limitNoMost rides to return. Default 10.
days_flexibleNoWith a date: also include rides this many days before and after it. Default 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-11-02 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-11-03 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  2. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-11-01 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-11-02 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  3. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-31 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-11-01 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  4. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-30 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-31 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  5. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-29 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-30 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  6. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-28 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-29 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  7. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-27 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-28 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  8. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-26 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-27 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  9. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-25 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-26 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  10. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-24 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-25 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  11. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-23 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-24 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  12. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-22 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-23 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  13. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-21 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-22 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  14. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-20 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-21 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  15. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-19 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-20 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  16. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-18 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-19 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  17. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-17 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-18 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  18. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-16 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-17 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  19. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-15 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-16 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  20. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-14 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-15 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  21. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-13 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-14 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  22. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-12 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-13 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  23. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-11 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-12 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  24. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-10 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-11 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  25. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-09 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-10 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  26. Changed1 schema field changed
    • changedInput schema / properties / date / description
      Previous value: -"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-07 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."New value: +"Optional travel date, YYYY-MM-DD (Pacific). Today is 2026-10-09 (Pacific): use today or a later date, and when the person names a day without a year, the next one on or after today. Omit to list the soonest rides."
  27. First observed

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare a safe, idempotent read, and the description still adds substantive behavior: nearby_rides is returned as a separate bucket with an instruction to label it as nearby, rides that stop in a city count for that city, and a ride-request link is included when nothing matches. It also discloses what the returned prices mean (all-in, fees included) and that booking happens off-tool via the link.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is front-loaded with identity and scope, then moves to inputs, then outputs, then edge cases — a sensible order. It is a single dense block, and the gas-splitting/empty-seats framing, while flavorful, partially restates what carpooling implies, keeping it just short of maximally tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the return-value burden and does so fully: route, departure date/time in Pacific, seats left, all-in USD price per seat, driver first name, and booking link. Combined with the nearby-rides and no-match behavior, an agent has everything needed to call it and interpret results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description earns a point by adding meaning the schema doesn't: from/to accept city or place names (with "San Francisco"/"Los Angeles" examples) and the stop-in-city matching rule that changes what results the parameters actually produce. Date and limit/days_flexible semantics are already fully documented in the schema and aren't repeated at length.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening names a specific verb and resource ("Find upcoming long-distance carpool rides on Seat Sherpa"), states the geographic scope (California and Nevada), and defines the marketplace model that makes the results interpretable (drivers selling empty seats, riders splitting gas). It also explicitly denies a capability ("this tool cannot book"), which separates it from a booking-style tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage context is clear: supply from/to and optionally a date, omit the date for soonest rides, and expect a request_ride_link fallback when nothing fits. It even routes agents to request_ride_link for the no-match case. It stops short of naming alternatives like get_ride (retrieve a specific ride) or list_service_areas, so an agent must infer when to search vs. look up a known ride.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources