developer-tools Static interface comparison
LetsFG — Flights & Hotels
2026.5.78 2026.5.79
No policy-significant interface change detected.
View the upgrade review as Markdown
A shareable summary of this comparison for an issue, pull request or ticket. Select the text and copy it.
INTERFACE DIFF
What changed, tool by tool
- 0Added tools
- 0Removed tools
- 1Modified tools
- 0Input-schema changes
- 0Output-schema changes
- 0Declared authority changes
1 tool with recorded changes
authenticateModifiedWhat changed
- authenticate: description changed.
Why it could matter
- Models choose and call tools partly from their descriptions.
What to verify
- Spot-check that agents still select this tool as intended.
- Declared effect
- unknown → unknown
- Description
- PreviousExplain how to connect a card so this server can search and book. Nothing is charged to connect — a 0.00 Revolut setup that saves the card so a booking can be charged later. Call with no arguments. It returns the current instructions and add_card_url (https://letsfg.co/connect). A PERSON must approve once in a browser — there is no endpoint that mints a token from card details, so do not ask the user for card numbers and do not try to automate this step. Two ways in: (a) add LetsFG as a connector in an assistant that supports remote MCP servers and approve it, or (b) any OAuth-capable client can register itself — see https://letsfg.co/for-agents, section "Option B". Both land on the same card screen. RETIRED 2026-09-02: the Stripe lanes (setup_url, setup_session_id, payment_method_id, card_token) and every token they issued. Passing them now fails. This does NOT create a Developer API billing account. Do not use connect_payment for this.
- CurrentExplain how to connect LetsFG so this server can search and book. Connecting is one tap at https://letsfg.co/connect and needs no card. Search works straight away. The card is asked for only at the first booking: book_flight returns an add_card_url for a 0.00 Revolut setup, nothing charged. Call with no arguments. It returns the current instructions and add_card_url. A PERSON must approve once in a browser — there is no endpoint that mints a token from card details, so do not ask the user for card numbers and do not try to automate this step. Two ways in: (a) add LetsFG as a connector (https://letsfg.co/mcp) in an assistant that supports remote MCP servers and approve it, or (b) any OAuth-capable client can register itself — see https://letsfg.co/for-agents, section "Option B". Both land on the same one-tap approval at letsfg.co/connect. RETIRED 2026-09-02: the Stripe lanes (setup_url, setup_session_id, payment_method_id, card_token) and every token they issued. Passing them now fails. This does NOT create a Developer API billing account. Do not use connect_payment for this.
Input schema
Input schema unchanged.
1 unchanged entry
(schema root)
No output schema is recorded for this tool in either release.
Link to this toolExact JSON from the published snapshots
Loads the exact recorded definitions of this tool from both releases. The full snapshots are linked under Evidence and provenance.
No tools match these filters.
13 tools with no recorded change
answer_booking_questionbook_flightbook_hotelcancel_hotel_bookingconnect_paymentget_agent_profileget_flight_bookingget_hotel_bookingload_resourcesresolve_hotel_cityresolve_locationsearch_flightssearch_hotels
Evidence and provenance
- Static findings
- PASS from Modelara’s automated analysis of the two declared interfaces. A policy outcome, not a security rating or a runtime test.
- Human review
- Automated static analysis. No reviewer decision is recorded for this comparison.
- Published evidence
- Part of Valyd’s published data generation listed in valyd-data-source.json. Published records are not rewritten.
Show provenance and exact files
- Comparison
letsfg/2026.5.78~2026.5.79The published comparison identifier.- Analyzer
modelara v0.1.8Policy version not recorded.Analyzed Nov 16, 2026, 11:15 PM UTC.- Distribution
npm- Previous release
letsfg-mcp@2026.5.7814 tools · published by the registry Oct 2, 2026, 2:01 PM UTCArtifact integritysha512-d2DnYkJwwhhZDBW9ccG/hp2Cu4F1l9Jgjeece5N1tSF0cgBkaOiBfXuM1tTXzA+WTB1+2OwCZrQmGR8cf0yJ1w==Interface fingerprintsha256:b88484616d004e86b030d393d9b2cbd39f50d84ea323952242b25f0f33cb95cdExact interface snapshot (JSON)- Current release
letsfg-mcp@2026.5.7914 tools · published by the registry Oct 17, 2026, 7:07 PM UTCArtifact integritysha512-+1PEL33HTWW/ZvxVzNi7q+zzgnGmcqzCM3lZBZIKSYf63dlsYqTCyTM7BW3Ovss+P1rZNgJc5HwtpBijIjb9QA==Interface fingerprintsha256:89c235e6a69825f303338dd4a631e142ec70ede88b45b8d124314743d2a6cb41Exact interface snapshot (JSON)- Comparison record
- Exact comparison record (JSON)
The integrity value or digest identifies the exact artifact that was inspected; it does not show that the package is safe. The interface fingerprint identifies the declared tools and schemas Modelara recorded for that release.
MODELARA ANALYSIS OUTPUT
Interface findings
Informational
1 findingauthenticateINFOChanged
What do these results mean?
- PASS
- No policy-significant interface change detected.
- REVIEW
- Interface changes require inspection.
- FAIL
- A policy-significant change was detected.
- INVALID
- The comparison could not be evaluated reliably.