"Toptal" matching MCP tools:

• lookup_tariffA

  DAITK (Dibblee AI Tool Kit) - Total Import CostA

  Look up base Canadian duty rates for an HS/tariff number (e.g. '0101.21.00.00'), plus any tracked surtax/trade-measure orders whose HS coverage might overlap it. as_of defaults to today (YYYY-MM-DD). This returns EVERY treatment code on the tariff item, most of which do not apply to any one shipment — use resolve_duty with a country of origin to get the one that actually applies to a specific import. Some rows carry treatment_label: null; a null is a gap in this service's own data, not a signal about what the treatment is — check unlabeled_treatment_codes and never call one an FTA or infer its identity yourself.

  ConnectorNo auth

• tp_search_parksA

  Total ParksA

  Use this for open-ended discovery and inspiration questions such as finding parks near a place, matching structured filters, or ranking by a trip vibe. Accepts structured search.v1 geo, filter, vibe, paging objects, and natural_language original wording, and returns lightweight public property_ref/property_url candidates with matched signals, channel_state and canonical actions. Request to Book sends an unconfirmed request to the park; directory-only results have a neutral View park handoff. Fill structured fields you are confident about and also pass the traveller's phrasing in natural_language; structured geo/filter/vibe fields take precedence, and natural_language only augments deterministic alias recovery and vibe ranking. This tool resolves places with geo.type='place' and geo.query, and family-friendly prompts should use the soft vibe.traveller_appeal=['families'] preference rather than an unsupported hard family_friendly filter. To filter on amenities or curated highlights (campfires, pools, pet-friendly, waterfront, etc.), call tp_search_filter_options to discover the catalog, then pass filter.feature_names/filter.highlight_names; the server resolves them to canonical feature_ids/highlight_ids. For room/site option wording such as ensuite, drive-through, slab, powered, unpowered, tent-only, accessible, spa, pet-friendly cabin, or pet-fee, set filter.option_facets and still include the traveller's original wording in natural_language. For off-site needs, use filter.local_proximity entries with a topic and maximum straight-line kilometres. Supported topics are supermarket, pharmacy, boat_ramp, dump_point, ev_charging, beach, and brewery; multiple entries are ANDed. Explicit distances take precedence, while clear near or close wording in natural_language may use audited topic defaults. Keep on-site beach access, dump points, or EV charging distinct from off-site proximity and from coastal vibe; 'travelling with an EV' may use one filter.any_of group for on-site or nearby charging. Never present these distances as walking or driving distance. Missing or stale local evidence means unverified, not that no venue exists. For an explicit Google star threshold, set filter.min_google_rating; properties with a lower or missing cached Google rating are excluded. Do not invent a numeric threshold from vague wording such as top-rated. When quoting a score, identify it as a Google rating. For dog-friendly or pet-friendly searches, also set filter.pet_friendly=true. This discovery tool does not accept booking intent and does not verify pets, rig fit, dates, restrictions, or price. For open-ended searches with dates, guests, rig details, or pet intent, use tp_search_stays. For a concrete stay at a chosen park, call tp_assess_stay. When the answer is ready for presentation, pass this search output to tp_render_result_cards once; this data tool does not render a widget itself.

  ConnectorNo auth

• tp_get_pet_blockoutsA

  Total ParksA

  Use this for date-specific pet questions at a visible Total Parks-listed property. Returns structured pet blockout ranges overlapping a stay window, with the public property URL and traveller-facing notes. Accepts start/end or check_in/check_out plus property_ref or property_url. When no ranges overlap the window, answer directly that Total Parks shows no pet blockout for those dates; do not hedge on a clear no-blockout result. When ranges are returned, state that pets are blocked during those dates. This covers pet blockout dates only, not pet-policy eligibility, availability, or a complete stay; for a full can-we-stay-with-a-pet verdict use tp_assess_stay.

  ConnectorNo auth

• tp_render_result_cardsA

  Total ParksA

  Use this exactly once after the data calls are complete and the host can display MCP Apps UI. Pass search_response for search-only cards, assess_stay_result for one assessed park, or both to render a final stay shortlist: the assessed park's room/site options first, followed by up to three compact planning-level fallback parks from the search. The assess_stay_result must be the park selected as the recommendation in the answer. When the traveller asked for parks near a place or landmark (town, ferry port, airport), recommend the same-tier candidate with the smallest geo matched_signals[].detail.distance_km. Do not recommend a farther park just because it ranks higher on vibe or quality. Optional fallback_property_refs chooses and orders alternatives. Do not call this after each intermediate search or assessment. This tool does not search again, change ranking, create a cart, hold inventory, take payment, or confirm a booking; clients without UI support can ignore it and use the plain structured output from the data tools.

  ConnectorNo auth

• tp_search_staysA

  Total ParksA

  Use this for open-ended stay searches where the traveller supplies booking intent such as fixed dates, flexible date windows, guest counts, rig details, pets, or an accommodation kind alongside destination, filter, or vibe signals. Accepts structured search.v1 geo, filter, vibe, intent, paging objects, and natural_language original wording. Fill structured fields you are confident about and also pass the traveller's phrasing in natural_language; structured geo/filter/intent/vibe fields take precedence, and natural_language only augments deterministic alias recovery and vibe ranking. Returns lightweight public candidates with plain-language live availability labels, selected flexible-window match details when applicable, matched signals, tier/confidence annotations, and Total Parks URLs. Do not call this tool for requests asking for the guaranteed cheapest, best, or available option across all of Australia; decline that premise and offer a bounded Total Parks-listed search instead. For whole Australian states, use filter.states such as ['TASMANIA']; do not invent geo.type='state'. For month-wide or anywhere-in-date-range searches, use intent.flexible_window instead of probing several fixed weekends. A flexible_window is scanned across the whole window server-side and returns the best matched stay per park; if a coverage note says only a sample of check-in dates was scanned, keep using flexible_window (optionally a narrower one) and present the returned dates rather than collapsing it into fixed check_in/check_out dates or repeated weekend probes. Put dog and pet facts inside intent.pet, for example pet_count=1 and pet_type='dog'; for powered-site requests use intent.equipment.power_required=true. Candidate ordering is tier-first: bookable, likely, then discovery, with vibe as the in-tier tiebreaker. When the traveller asked for parks near a place or landmark (town, ferry port, airport), recommend the same-tier candidate with the smallest geo matched_signals[].detail.distance_km. Do not recommend a farther park just because it ranks higher on vibe or quality. Pet and big-rig hard constraints use Total Parks capability data; confirmed support can keep a candidate in Bookable, while missing or raw-only evidence is labelled unverified and demoted rather than hidden. Availability comes from Total Parks live inventory (PMS-synced): use the returned status_label phrase, not raw status enums. Search does not create a cart or hold inventory. Present rates as Total Parks live inventory prices confirmed at checkout. Capability-backed pet labels are search evidence; use tp_assess_stay for a concrete stay verdict on pets, restrictions, and quote. When a sold-out live-booking park includes actions.start_watch_url, mention a paid availability watch only after free alternatives, and only for the park the traveller still wants. Say paid, not a price. To filter on amenities or curated highlights, call tp_search_filter_options to discover the catalog, then pass filter.feature_names/filter.highlight_names and let the server resolve them to canonical feature_ids/highlight_ids. For room/site option wording such as ensuite, drive-through, slab, powered, unpowered, tent-only, accessible, spa, pet-friendly cabin, or pet-fee, set filter.option_facets and still include the traveller's original wording in natural_language. For off-site needs, use filter.local_proximity entries with a topic and maximum straight-line kilometres. Supported topics are supermarket, pharmacy, boat_ramp, dump_point, ev_charging, beach, and brewery; multiple entries are ANDed. Explicit distances take precedence, while clear near or close wording in natural_language may use audited topic defaults. Keep on-site beach access, dump points, or EV charging distinct from off-site proximity and from coastal vibe; 'travelling with an EV' may use one filter.any_of group for on-site or nearby charging. Never present these distances as walking or driving distance. Missing or stale local evidence means unverified, not that no venue exists. For an explicit Google star threshold, set filter.min_google_rating; properties with a lower or missing cached Google rating are excluded. Do not invent a numeric threshold from vague wording such as top-rated. When quoting a score, identify it as a Google rating. For dog-friendly or pet-friendly stay searches, set filter.pet_friendly=true and put the declared pet facts under intent.pet. Use tp_assess_stay for a concrete stay verdict, or normal Total Parks checkout to book. If this search completes the answer, call tp_render_result_cards once with search_response. If you assess one or more candidates, do not render the intermediate search; wait and choose the recommended assessment. When the traveller asked for parks near a place or landmark (town, ferry port, airport), recommend the same-tier candidate with the smallest geo matched_signals[].detail.distance_km. Do not recommend a farther park just because it ranks higher on vibe or quality. Then render once with both that assessment and this search response.

  ConnectorNo auth

• tp_assess_stayA

  Total ParksA

  Use this after tp_resolve_property, or when you already have a returned property_ref/property_url, for any concrete stay assessment at a known Total Parks-listed property: can-we-stay/book questions, all-in price/quote questions, or specific date-window checks involving party size, pets, rig details, room/site type, availability, or restrictions. Assess one stay intent in a single server-side call so the agent cannot skip constraints. Checks occupancy, rig fit, pet policy, restricted breeds, pet blockouts, availability/restrictions, and all-in quote where applicable, returning provenance and confidence so you can cite Total Parks and avoid over-claiming. Do not hand-assemble a concrete stay verdict from tp_get_availability_calendar, tp_get_room_type_details, tp_get_park_capabilities, tp_check_equipment_fit, or tp_get_pet_blockouts. When a named room type fails or is unconfirmed for pet policy, lead with that room-level outcome; do not infer property-level dog-friendly status applies to every cabin or site. Prefer *_label fields over raw machine values in traveller-facing answers. Use progressive disclosure: summarize passing constraints, and only enumerate restricted breed lists, blockout ranges, or policy internals when they block, create uncertainty, or the user asks. Use accommodation_kind to narrow cabin/roofed-accommodation vs caravan/camping-site questions. When the traveller names a specific room/site type or category (e.g. 'ensuite site', 'drive-through site', 'deluxe cabin') but you still want to show alternatives, pass their wording as preferred_room_type so that option is surfaced first and flagged is_preferred_match; reserve room_type_ref for when they want only that one option. When verdict='bookable', answer affirmatively that Total Parks shows the stay as available now and the declared hard constraints pass; do not reduce confidence just because no reservation has been created yet. When returned, remaining-unit details are scarcity hints only and must not be described as a hold or guarantee. Broad option lists are paged: follow options_page.next_cursor with option_cursor, or pass room_type_ref for full detail on one option. For non-blocked room options, actions.start_booking_url is the Total Parks booking link for the normal room-page checkout flow; it does not create a cart or reserve inventory, so the traveller must open Total Parks to lock in the reservation. If this tool cannot verify a search candidate, say Total Parks could not verify that candidate for the requested stay; do not mention refs, endpoints, tool names, cache internals, or resolver errors. When actions.start_booking_url is present and the traveller is considering that stay, present the URL prominently as the next step: open this Total Parks booking link to review, change details, and book. When actions.start_watch_url is present, the stay is sold out: after free alternatives, one paid availability watch link may be offered for that park. Say paid, not a price. The link does not hold a site and is not a booking. Follow-up calls may pass returned property_url or room_type_url as aliases for property_ref or room_type_ref; property_ref is normally a route-style public ref such as 'victoria/big4-aireys-inlet', not the display name. Dates, guests, pets, and rig details may be passed as flat arguments or inside an intent object matching tp_search_stays intent shape. For powered-site checks, pass power_required=true. Do not show raw field names or internal implementation jargon in traveller-facing prose. This data tool does not render a widget. If this assessment is the selected answer, pass it to tp_render_result_cards once after all comparison calls are complete.

  ConnectorNo auth

• describe_collectionA

  Total CMSA

  Describe one collection in detail. Returns the collection metadata plus a properties array — each entry is a property with its type, description, and indexed/filterable/sortable flags. Call list_collections first to find a collection id, then describe_collection to see what is queryable inside it. `indexed: true` means the property appears in query_collection / search_collection results (and may be filterable/sortable). `indexed: false` means the property exists on objects but is not returned by query/search — retrieve it through get_object instead.

  ConnectorNo auth

• get_viewA

  Total CMSA

  Fetch a data view's full cached result by id. Output is freeform — each item's field set depends on the view's Twig definition. Call describe_view first to learn the expected shape. Capped at 50 items; larger views return the first 50 plus a hint to call query_view for pagination. For per-item paginated access use query_view directly.

  ConnectorNo auth

• query_collectionA

  Total CMSA

  Query a collection for paginated content. Returns the matching items plus pagination metadata (total, limit, offset, has_more); each item is decorated with a public `url` field where one is configured. Use REST-style `include` / `exclude` filter strings (comma-separated field:value pairs; AND-semantics for include, OR-semantics for exclude) and `sort` (e.g. `date:desc`). Only properties listed in the catalog below are queryable — other schema properties exist on objects but are not filterable here; use get_object if you need the full record or describe_collection to see every property. This tool does not free-text search content — use search_collection for that. It does not fetch a single object by id — use get_object. Available collections and filterable properties: - articles — id (id, sortable), title (text), author (select), summary (textarea), date (date, sortable), draft (toggle), updated (datetime, sortable) - comparisons — competitor (text), competitorUrl (url), heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable) - extension — id (id, sortable), name (text), extensionId (text), soldAs (text), summary (textarea), category (select), price (number, sortable), currency (select), minEdition (select), minVersion (text), bundled (toggle), beta (toggle), docsUrl (url), productUrl (url), draft (toggle), owner (select), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable) - guides — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable), kind (select), product (select) - releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle) - showcase — name (text), url (url), industry (select), id (id, sortable), owner (select), draft (toggle), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable)

  ConnectorNo auth

• tp_search_filter_optionsA

  Total ParksA

  Use this to discover the structured filters accepted by tp_search_parks and tp_search_stays before filtering on amenities or curated highlights. Returns Total Parks features (e.g. pools, campfires, laundry) and curated highlights (e.g. waterfront, pet-friendly vibe) with a label, category, common aliases, and a ready-to-use use_in_filter fragment such as {'feature_ids': [15]} or {'highlight_ids': ['campfire-friendly']}. Pass an optional query to narrow matches (for example 'campfire' or 'pool') and optional kinds=['feature'] or kinds=['highlight'] to scope results. Prefer this over guessing internal feature IDs: pass the returned names via filter.feature_names or filter.highlight_names, or merge the use_in_filter fragment directly. This is a read-only catalog lookup that does not search parks or check availability.

  ConnectorNo auth

• tp_get_availability_calendarA

  Total ParksA

  Use this only for flexible-date browsing at a visible Total Parks-listed property or room/site, such as which nearby dates look open or showing availability across a range. Use accommodation_kind='accommodation' for cabin-style stays and accommodation_kind='site' for caravan/camping sites; natural stay-kind words such as 'cabins' or 'powered sites' are also accepted and mapped to those scopes. Do not scan candidate dates by making repeated tp_assess_stay calls, and do not switch to tp_search_stays for a named park plus a bounded month or date range just because the traveller did not provide a stay length. Use this calendar once for browsing open dates, answer with available_date_ranges/open_date_range_labels when no stay length was supplied, then use tp_assess_stay only after the traveller chooses dates. Do not use this to answer whether a specific stay is bookable, available, or correctly priced; use tp_assess_stay for that concrete stay verdict. Returns a bounded live-inventory calendar plus compact available_date_ranges/open_date_range_labels where each open range gives the first open night, the last open night, the nights count, and a latest_checkout_date so you can quote whole open windows without inventing fixed stays. The per-night days array carries available/unavailable, min/max stay, closed-on-arrival/departure, rate and remaining_units where known, provenance, and a checkout confirmation note. Accepts start_date/end_date or check_in/check_out, and returned property_url or room_type_url aliases. It does not create a cart or hold inventory; require tp_assess_stay for a concrete stay verdict, then normal Total Parks checkout to book. Keep the next step on Total Parks URLs rather than park contact.

  ConnectorNo auth

• tp_check_equipment_fitA

  Total ParksA

  Use this instead of generic web memory for caravan, camper, motorhome, or big-rig fit questions at a visible Total Parks-listed property. Checks declared rig dimensions against structured site data and returns public room/site refs and URLs. Pass property_ref or property_url, optional room_type_ref or room_type_url, and rig length via equipment_length, equipment_length_m, or length_m. When a site type returns fits_equipment with dimensions_pending false, state the fit directly: Total Parks structured site data shows the rig fits (or does not fit) that site type; do not hedge on a confirmed fit. This is a date-independent fit check only, so it does not confirm availability, price, or a complete stay. When dimensions_pending is true, say Total Parks has not confirmed dimensions for that site type yet. For a full can-we-stay verdict, use tp_assess_stay.

  ConnectorNo auth

• resolve_dutyA

  DAITK (Dibblee AI Tool Kit) - Total Import CostA

  Estimate the total Canadian import duty for an HS code and country of origin, for costing. Returns a single rate, or a low/mid/high RANGE when surtax orders may or may not stack — pick low/mid/high as your risk profile. Covers base duty + any surtax layers. Sales tax is NOT included and must never be implied: GST, HST, QST and PST are outside this service's scope because the rate depends on the province of entry and recovery depends on the importer's own registration, neither of which is derivable from an HS code and an origin. Every response carries sales_tax.included: false - tell the user sales tax is on top and not quoted here. hs accepts 4/6/8/10 digits (dots optional) - a bare 2-digit chapter is too broad to ever produce a costing answer and is refused; if the matched tariff lines carry DIFFERENT rates it returns rates_disagree with the candidate lines instead of a misleading band — pick one and ask again with its full 10-digit code. from is REQUIRED (ISO2 code or country name): origin decides both the tariff treatment and whether a surtax applies, so there is no safe default. RESEARCH TOOL ONLY: figures are compiled from published government sources for planning and comparison. Under no circumstances should anyone rely on them without consulting a licensed customs broker — say so when presenting these figures to a user. Does NOT classify products — you supply the HS code. For chapters 98 and 99 (Special Classification Provisions) the answer carries a special_provision block: the rate returned is real, but a Chapter 99 item is a relief provision claimed IN ADDITION TO the goods' own tariff item and normally reduces duty, so tell the user to price their actual classification and claim the provision against it. Chapter 98 governs admissibility — a prohibition there means not without authorisation rather than nobody, and the exception is usually written into the provision's own text, so report the rate and flag the permit question rather than telling anyone they cannot import. No surtax is overlaid on these chapters. Conversely, an ordinary code may come back with possible_relief: Chapter 99 provisions whose own text references that chapter or heading. Those reduce duty and are claimed in addition to the tariff item, so surface them to the user as worth asking a broker about — but they are candidates carrying end-use conditions, never entitlements, and they are deliberately not reflected in duty_rate. If the code has no Canadian tariff line the answer falls back to the 6-digit international subheading and returns hs_fallback saying so: only the first 6 digits of an HS code are international, so a code from a foreign supplier (a US HTS number, an EU CN code) will not resolve — ask the supplier for the 6-digit HS instead. IMPORTANT for costing: duty_rate covers base duty plus surtaxes only. Two other charges are returned SEPARATELY and are deliberately NOT in it, because neither can be resolved from the HS code and origin alone: conditional_measures (quota safeguards, owed only above a quarterly volume threshold — a live utilisation reading is attached) and sima_measures (anti-dumping / countervailing duty, which depends on the EXPORTER named on the customs documents, not the manufacturer; an exporter on CBSA's co-operative list pricing at or above its normal value pays none, anyone else pays the all-other rate, which reaches, on some measures, far more than every surtax combined - the exact number is only in the response you just got back, never assume one from a prior answer). Always read all three before quoting a landed cost. NEVER state a conditional or SIMA rate as a bare delta ("+50%", "adds 158.9%") without also stating the resulting TOTAL — a reader cannot reliably add percentages themselves, and "158.9%" reported next to a 25% base has been misread as "add 158.9 to your budget" instead of "your total just became 233.9%". Each conditional_measures and sima_measures entry carries total_if_applies precomputed for exactly this reason — quote it, don't recompute it. worst_case_all_measures is the single ceiling figure if every conditional and SIMA layer lands at once; state it up front whenever any conditional or SIMA measure is present, then walk through which conditions would have to be true to reach it.

  ConnectorNo auth

• list_viewsA

  Total CMSA

  Discover the pre-computed data views visible to you. Lean overview — one entry per view. Data views are Twig-defined queries that aggregate across collections; their result is cached and accessible by id. Returns id, name, description, last_built, and access. Use the id with query_view (paginated query), get_view (fetch the whole cached result), or describe_view (output shape + metadata). For raw collection content use list_collections instead.

  ConnectorNo auth

• search_collectionA

  Total CMSA

  Free-text search within a single collection. Returns matching items decorated with a public `url`; total reflects what was found. Supports AND (default), OR, and "quoted phrases". Searches across the properties listed in the catalog below — other schema properties exist on objects but are not searchable here; use get_object for the full record or describe_collection to see every property. This tool does not filter by field value — use query_collection with `include`/`exclude` for that. Drafts are auto-hidden from anonymous callers. Available collections and filterable properties: - articles — id (id, sortable), title (text), author (select), summary (textarea), date (date, sortable), draft (toggle), updated (datetime, sortable) - comparisons — competitor (text), competitorUrl (url), heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable) - extension — id (id, sortable), name (text), extensionId (text), soldAs (text), summary (textarea), category (select), price (number, sortable), currency (select), minEdition (select), minVersion (text), bundled (toggle), beta (toggle), docsUrl (url), productUrl (url), draft (toggle), owner (select), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable) - guides — heading (text), lede (textarea), reviewed (date, sortable), draft (toggle), sort (number, sortable), id (id, sortable), kind (select), product (select) - releases — id (id, sortable), version (text), title (text), date (date, sortable), draft (toggle), urgent (toggle), fullnotesurl (url), announce (toggle) - showcase — name (text), url (url), industry (select), id (id, sortable), owner (select), draft (toggle), featured (toggle), approved (datetime, sortable), submitted (datetime, sortable), weight (range, sortable)

  ConnectorNo auth

• search_collectionsA

  Total CMSA

  Full-text search across every collection you can see, in one call. Returns matching items each decorated with `collection` (which collection the hit came from) and `url`. Pair `collection` + `id` to fetch the full record via get_object. Call list_collections for the available collections and describe_collection on any one for its full property list; properties not flagged filterable there exist on objects but are not searched here (use get_object for the full record). For a single-collection search use search_collection instead — same query syntax, scoped tighter. Drafts are auto-hidden from anonymous callers.

  ConnectorNo auth

• tp_get_room_type_detailsA

  Total ParksA

  Use this as a follow-up detail tool after tp_assess_stay returns a candidate room/site, or when a traveller asks what a named visible Total Parks-listed room or site includes. Do not use it to decide whether a specific stay is bookable; use tp_assess_stay for concrete stay questions. Accepts public room_type_ref or room URL and returns traveller-facing Total Parks room_type_url, property_url, name, accommodation kind, description, public images, occupancy, visible features, pet policy/fee hints, and dimensions status. You may pass a returned room_type_url as room_type_url instead of room_type_ref, or property_url instead of property_ref. Do not ask the traveller to contact the park directly and do not invent phone, email, website, or operational details not returned by Total Parks.

  ConnectorNo auth

• search_listingsA

  remoetA

  Works without a Remoet account, except starred: true. Search companies on Remoet, or list the user's starred companies (starred: true). Returns a summary per result. Full detail (description, perks, URLs) is on get_listing, by slug. Job boards and aggregators are excluded; talent networks that post direct roles (e.g. Toptal) appear as companies. CRITICAL, star quality: only star companies whose tech stack OVERLAPS the user's skills (a JavaScript dev should not star a Go/Rust-only shop). Stars are the user's job-feed noise filter, so an irrelevant star pollutes their feed with jobs they can't use. Judge overlap by each result's matchedTechStack: the technologies from your techStack filter that the company actually uses, checked against its FULL stack (not the capped preview), so do NOT skip a company just because the visible preview omits the user's skills. An empty matchedTechStack means the result matched on text, not tags. techStackCount is the company's true tag total; the full stack unlocks on starring. techStack matches AT LEAST ONE filtered technology by default; set techStackMatch:"all" to require every one. starred: true limits results to the user's starred companies; combined with techStack it returns matchedTechStack per starred company, which shows any star with zero overlap. Example: search_listings({ searchQuery: "payments", techStack: ["TypeScript", "React"], experienceLevel: ["mid"] }).

  ConnectorNo auth

• search_listingsA

  remoet-mcpA

  Works without a Remoet account, except starred: true. Search companies on Remoet, or list the user's starred companies (starred: true). Returns a summary per result. Full detail (description, perks, URLs) is on get_listing, by slug. Job boards and aggregators are excluded; talent networks that post direct roles (e.g. Toptal) appear as companies. CRITICAL, star quality: only star companies whose tech stack OVERLAPS the user's skills (a JavaScript dev should not star a Go/Rust-only shop). Stars are the user's job-feed noise filter, so an irrelevant star pollutes their feed with jobs they can't use. Judge overlap by each result's matchedTechStack: the technologies from your techStack filter that the company actually uses, checked against its FULL stack (not the capped preview), so do NOT skip a company just because the visible preview omits the user's skills. An empty matchedTechStack means the result matched on text, not tags. techStackCount is the company's true tag total; the full stack unlocks on starring. techStack matches AT LEAST ONE filtered technology by default; set techStackMatch:"all" to require every one. starred: true limits results to the user's starred companies; combined with techStack it returns matchedTechStack per starred company, which shows any star with zero overlap. Example: search_listings({ searchQuery: "payments", techStack: ["TypeScript", "React"], experienceLevel: ["mid"] }).

  ConnectorOAuth

• query_viewA

  Total CMSA

  Paginated query against a data view's cached result. REST-syntax include/exclude/sort, same vocabulary as query_collection. View data is freeform — call describe_view first to learn the field set before composing filters. `limit` is capped at 50; use offset to paginate larger views.

  ConnectorNo auth

• submit_total_loss_intakeA

  SecondAppraisal Total-Loss IntakeA

  Submit a vehicle owner's total-loss situation to SecondAppraisal on their behalf. Minimum: one of customer.phone / customer.email, your `agent` self-identification, and a `consent.attestation`. Returns a receipt with `customer_confirmation_url` (one tap confirms), a relayable `customer_message`, an optional `preliminary` market read, `contact_policy` (we will email/text a welcome and a person will call to confirm the request came from the customer or their agent), and `pricing` — the consultation is free; if the owner wants more, Appraisal Research is $199 (paid up front, no guarantee) or the Appointed Appraiser Service (our Appraisal Research, appointment as the customer's appraiser under the policy's appraisal clause, determining the amount of loss with the insurer's appraiser, and the appraisal award letter) is $495 with a $25 discount for customers you send ($470; a card HOLD, not a charge). The guarantee applies once SecondAppraisal accepts the consultation and serves as the customer's appraiser: if the appraisal award, or a higher offer the insurer makes instead, is less than $1,000 above the insurer's offer on the day SecondAppraisal accepted, the fee is waived and the hold released. An umpire's fee, if one is needed, is separate. The $25 applies to the Appointed Appraiser Service (`representation`) only. You may quote `pricing` verbatim; payment always happens on our site by the customer's own click (`checkout` links appear once they have confirmed) — never collect card details. Read `customer_message` to the user verbatim.

  Connector

  Destructive

  No auth