Skip to main content
Glama
Sign In

Seat Sherpa

by app.seatsherpa
OverviewDiscussionsAdmin

Link to request a Seat Sherpa ride

request_ride_link
Read-onlyIdempotent

For a rider when no ride fits: a link where the person posts a ride request on Seat Sherpa, the carpool marketplace, so drivers on that route see it and get notified, and the person hears back when a matching ride is posted. Use it after search_rides finds nothing that works (that answer already includes this link), or when the person asks to be told about a trip nobody has posted. Takes the same places and optional date as search_rides. The person signs in and posts the request on the page; this tool only builds the link, posts nothing, and never needs names, phone numbers or emails.

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 and the person picks the date on the page.
fromYesWhere the rider starts: a city or place in California or Nevada, e.g. "San Francisco", "UC Davis", "Irvine".
seatsNoOptional: seats the rider needs, 1 to 4. Only mentioned in the answer; the person picks it on the page.

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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  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 and the person picks the date on the page."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 and the person picks the date on the page."
  27. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say read-only/open-world/idempotent; the description adds substantive behavior: the tool builds a link and posts nothing, the person signs in and submits on the page, and no names/phone/emails are needed. That clarifies where the side effect actually occurs, which annotations cannot convey.

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?

Front-loaded with the purpose and the when-to-use rule before the marketplace explanation. It is one long, somewhat run-on paragraph, and the drivers-get-notified clause is explanatory rather than operational, but virtually every sentence still earns its place.

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

Completeness4/5

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

Covers trigger conditions, mutation-free behavior, privacy constraints, and parameter mapping for a 4-parameter tool with full schema coverage and no output schema. The only soft gap is that the returned value (the link itself) is implied by the title rather than stated explicitly.

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 schema already documents all four parameters. The description adds cross-tool meaning — 'takes the same places and optional date as search_rides' — grounding argument shape in a sibling the agent already knows, and notes seats is informational only.

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?

States a specific verb+resource: a link the rider uses to post a ride request on Seat Sherpa, and describes the downstream effect (drivers on the route get notified, rider hears back). It is clearly distinct from search_rides (which finds rides) and post_ride_link (the driver-side link) without needing either schema.

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

Usage Guidelines5/5

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

Explicit trigger conditions: after search_rides returns nothing usable, or when the person asks to be notified about a trip nobody has posted. It also warns that search_rides already embeds this link, which prevents redundant calls — a real routing rule rather than vague context.

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

All Seat Sherpa toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources