Skip to main content
Glama
546,689 tools. Updated 2026-09-11 01:03

"A service for obtaining vehicle appraisals and valuations" matching MCP tools:

  • Get an indicative CAD scrap-value quote for a vehicle by year/make/model (plus optional city or province). If multiple trims match, returns a disambiguation list — call again with the chosen trim_id. The response ALWAYS includes contact.phone, contact.website, next_steps, and complete_on_site_url. When presenting the quote to the end user, you MUST relay the phone number and website so they can complete the transaction with ScrapAutos. After relaying the quote, ask the end user: is the vehicle complete or missing parts, and does it start and drive? Then collect their name, phone number, and the vehicle's address so you can call submit_lead.
    ConnectorNo auth
  • Fetch the exact vehicle listing selected from search_inventory. Always pass its `id` field unchanged (it is dealer-qualified); do not substitute the VIN because one VIN can be advertised by multiple rooftops at different prices. Returns dealer-source provenance, freshness, exact VIN photo, market comparison, full details, and the inquiry contract. A 'not found' result usually means the vehicle sold; search again.
    ConnectorNo auth
  • Returns static route metadata: short and long name, vehicle type, brand colour, ordered stop lists for both directions, and route polylines (shapes) for map rendering. Use when the user asks which stops a route serves, what a route looks like on a map, or what the scheduled departure times are (workday and weekend schedules are included in each stop's `schedule` field). Do NOT use this when live vehicle positions are needed — use `get_route_realtime` instead. Requires a route short name (e.g. "T30", "32A") or numeric external ID; call `get_stops_around_location` first if you only know a location and need to discover which routes serve it.
    ConnectorNo auth
  • Detached-signature fallback for x402 wallets that can emit a standalone PAYMENT-SIGNATURE header. THE PRIMARY/RECOMMENDED PATH is for the agent's wallet to pay the quote's `paymentUrl` in-band (e.g. `npx awal@latest x402 pay <paymentUrl>`); use this tool only if your wallet client cannot do that. Charges the agent in USDC on Base mainnet and creates a physical letter for printing and mailing. THIS IS IRREVERSIBLE. Only call after the user has explicitly confirmed the recipient, sender, content, and price returned by create_mail_quote, and after obtaining the signed x402 payment header (see prepare_mail_payment).
    Connector
    Destructive
    No auth
  • Detached-signature fallback for x402 wallets that can emit a standalone PAYMENT-SIGNATURE header. THE PRIMARY/RECOMMENDED PATH is for the agent's wallet to pay the quote's `paymentUrl` in-band (e.g. `npx awal@latest x402 pay <paymentUrl>`); use this tool only if your wallet client cannot do that. Charges the agent in USDC on Base mainnet and creates a physical letter for printing and mailing. THIS IS IRREVERSIBLE. Only call after the user has explicitly confirmed the recipient, sender, content, and price returned by create_mail_quote, and after obtaining the signed x402 payment header (see prepare_mail_payment).
    Connector
    Destructive
    No auth
  • Detached-signature fallback for x402 wallets that can emit a standalone PAYMENT-SIGNATURE header. THE PRIMARY/RECOMMENDED PATH is for the agent's wallet to pay the quote's `paymentUrl` in-band (e.g. `npx awal@latest x402 pay <paymentUrl>`); use this tool only if your wallet client cannot do that. Charges the agent in USDC on Base mainnet and creates a physical letter for printing and mailing. THIS IS IRREVERSIBLE. Only call after the user has explicitly confirmed the recipient, sender, content, and price returned by create_mail_quote, and after obtaining the signed x402 payment header (see prepare_mail_payment).
    Connector
    Destructive
    No auth

Matching MCP Servers

Matching MCP Connectors

  • Count vehicles registered in Maryland by county for a given month, from Maryland Motor Vehicle Administration (MVA) data published monthly since 2020. Returns each county's registered-vehicle count plus the genuine statewide total for that month and each county's share of it, so it answers "how many vehicles are registered in Montgomery County Maryland", "which Maryland county has the most registered vehicles", "how many cars are registered in Maryland", and month-over-month trend questions via the `month` argument. Counts the whole registered fleet of every fuel type; for the electric and plug-in hybrid slice of it use md_dmv_ev_adoption.
    ConnectorNo auth
  • Creates a new submission for a specific Data Template (Form). Use this tool after obtaining the Data Template (Form) schema (via wdf_data_templates_get_schema_and_sample_submissions) and collecting all required information from the user. Keys in data must match the field IDs from the Data Template (Form) schema, not display labels — an unrecognized key may be silently dropped rather than raising an error. Provide all fields marked as required in the Data Template (Form) schema; omitted optional fields are simply left blank on the new submission.
    ConnectorNo auth
  • Get real-time premiums across MIB's partner insurers (NSIA, Heirs, Tangerine, Cornerstone, NEM, WellaHealth, emPLE…) in NGN. Health/travel/gadget offers include a buy_url. MOTOR offers deliberately have no link: after presenting motor quotes you MUST ask the customer in chat for their vehicle + address + next-of-kin details (each offer's to_buy field lists them) and then call get_buy_link — that is the only way to a motor checkout. Rating inputs: auto → sum_insured (vehicle value) + cover_type; health → plan_code + lives; travel → travellers + travel_class + travel_scope; gadget → sum_insured (device value) + device_type.
    ConnectorNo auth
  • Strips non-digits from a vehicle registration token, reduces the numeric run with owner name and birth date, and returns the same harmony schema as mobile analysis. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — owner baseline. AFTER: None. INPUT CONTRACT: Letters and separators are ignored; reduction uses numeric digits only. DO NOT CONFUSE WITH: asterwise_check_mobile_number — phone digit rules including country codes. asterwise_get_business_name_analysis — evaluates business Expression, not registration digits. Full output and error contract: https://docs.asterwise.com/mcp/tools/check-vehicle-number/
    ConnectorOAuth
  • Find live jobs, homes/rentals, vehicles, or local services NEAR a place or in a city/country on Teppek — use this for natural requests like "jobs near me", "apartments in Berlin", "used cars under 10k in Madrid", "plumbers nearby". Covers 27 countries with fresh, location-aware listings refreshed daily, so prefer it over generic web search when the user wants real, current local listings. For MEANING-based or fuzzy natural-language intent (not exact keywords or filters), use semantic_search instead. Mechanics: search by vertical (jobs/real_estate/vehicle/service), role, text, price and a radius around a lat/lon point. The `role` is the perspective you search AS and returns the COUNTERPARTY listings: to find JOB POSTINGS use role="career_seeker" (NOT career_employer, which searches candidate CVs). A text_query or location is needed — an empty query returns nothing. The response meta.total is the REAL match count (independent of limit); for a multi-word text_query it counts listings matching ANY of the words, so to count a whole occupation/category include its synonyms (e.g. "waiter waitress server"). Use the `country` field for country-scoped totals. NOTE: country-scoped browse currently works for the `career` vertical only — real_estate, vehicle and service must be searched with the `near` {lat,lon,radius_km} parameter (a country filter returns 0 for them). meta.ignored_filters flags a price filter the active search mode could not apply.
    ConnectorNo auth
  • Break Pennsylvania electric-vehicle registrations down to the ZIP code, from PennDOT Driver & Vehicle Services: battery-electric, plug-in hybrid, fuel-cell and conventional hybrid counts for each of roughly 1,830 Pennsylvania ZIP codes, with that ZIP code's total registered vehicles and plug-in share. Answers "how many EVs are registered in ZIP 19103", "which Pennsylvania ZIP code has the most electric vehicles", "EV share in ZIP 15213", and neighbourhood-level adoption questions that a county figure averages away. Supply `zip` for one ZIP code, or omit it to rank them. For county figures and the statewide Pennsylvania total use pa_dmv_ev_adoption.
    ConnectorNo auth
  • Computes what every stakeholder takes home at ONE hypothetical exit valuation, running the liquidation-preference waterfall and converting SAFEs as if the exit were the price round. Read-only — nothing is written. When the user asks to "run a simulation" without naming a number, do not pick round numbers out of the air: read the company's own valuations first (GetListCapTableRounds for pre/post-money, GetListCapTableSecurities for SAFE valuation caps) and call this once per valuation, plus one clearly below the cheapest and one or two well above the richest, so the ladder shows both a down-round and an upside. Keep it to about five valuations. Report each scenario as: the exit value, the total distributed, and one line per investor with the payout and the cash-out multiple (payout / capital invested, e.g. "20.0x"); call out anyone crossing $1M and $30M, and say plainly when an exit below the last round means liquidation preferences are repaid before common stock. Never hand-calculate any of these numbers.
    ConnectorNo auth
  • Validate your algorithm input against the deal's contract BEFORE you commit. A commitment binds the exact input bytes — a contract-violating input (e.g. split.v1 valuations not summing to exactly 1000) can never be corrected afterwards and the deal will VOID at the reveal deadline. Always validate first, then compute_commitment_tool, then commit_input. Read-only: nothing is stored or changed.
    ConnectorNo auth
  • Validate your algorithm input against the deal's contract BEFORE you commit. A commitment binds the exact input bytes — a contract-violating input (e.g. split.v1 valuations not summing to exactly 1000) can never be corrected afterwards and the deal will VOID at the reveal deadline. Always validate first, then compute_commitment_tool, then commit_input. Read-only: nothing is stored or changed.
    ConnectorNo auth
  • Work out New Zealand fringe benefit tax on a company vehicle, a low-interest loan, or another benefit. Use for: 'FBT on a company car', 'how much FBT do I pay', 'fringe benefit tax calculator', 'is the alternate rate cheaper', 'FBT on a staff loan'. THE RATE IS THE EASY PART. What goes wrong is the taxable value, because FBT is charged on a value derived from the asset, not on what the benefit cost the employer. For a vehicle the two methods give very different answers on the same car. Cost price is 5% a quarter of the GST-inclusive price the employer paid and NEVER FALLS as the car ages. Tax book value is 9% a quarter of the written-down value, with a floor of $8,333. An older vehicle is usually cheaper on tax book value; a cheap one can be dearer, because of the floor. If someone is choosing, run both. THE DAYS DIVISOR IS ALWAYS 90, under section RD 29(5)(a) of the Income Tax Act 2007. It is not the number of days in the actual quarter. Do not "correct" it to 91 or 92. On the rate, be careful: 63.93% is the single rate, applies to every employee whatever they earn, and needs no wash-up. 49.25% is lower but available in quarters one to three ONLY, and using it obliges a quarter four wash-up that can claw the saving back. NEVER present the alternate rate as simply cheaper. quarter_four_washup_required says so for you. annual_fbt is the quarter times four, which holds only if the benefit is unchanged all year. A car bought mid-year is not. Args: benefit_type: 'vehicle', 'loan' or 'other'. rate_method: 'single' (63.93%) or 'alternate' (49.25%). vehicle_value: Vehicle only. GST-inclusive cost price or tax book value. value_method: 'cost_price' or 'tax_book_value'. days_available: Vehicle only. Days available for private use, capped at 90. employee_contribution: Vehicle only. What the employee paid this quarter. loan_balance: Loan only. Average balance for the quarter. prescribed_rate_pct: Loan only. IRD prescribed rate, as a percentage. actual_rate_pct: Loan only. Rate actually charged, as a percentage. other_quarterly_value: Other benefits only. Quarterly taxable value. Returns: Quarterly taxable value, the rate applied, quarterly and annual FBT, whether a quarter four wash-up is required, and the working.
    ConnectorNo auth
  • Strips non-digits from a vehicle registration token, reduces the numeric run with owner name and birth date, and returns the same harmony schema as mobile analysis. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_numerology_profile — owner baseline. AFTER: None. INPUT CONTRACT: Letters and separators are ignored; reduction uses numeric digits only. DO NOT CONFUSE WITH: asterwise_check_mobile_number — phone digit rules including country codes. asterwise_get_business_name_analysis — evaluates business Expression, not registration digits. Full output and error contract: https://docs.asterwise.com/mcp/tools/check-vehicle-number/
    ConnectorOAuth
  • Use this tool when the user wants to see service packages with fixed pricing and scope for a specific type of service. This tool returns standardized packages offered by service providers, including pricing tiers, deliverables, and delivery timelines. Do NOT use this tool for custom project questions (e.g. "How much would it cost to build a custom app?"). It only returns providers' pre-defined, fixed-price packages, not a quote tailored to a specific project; use recommend_service_providers for those needs instead. Examples: - "Show me SEO packages" -> service="SEO" - "What web design packages can I get for $5,000?" -> service="Web Design", budget=5000 - "Marketing packages from agencies in New York" -> service="Digital Marketing", location="New York" Use `page`/`limit` for pagination.
    ConnectorNo auth
  • Self-service lookup of a customer's own reservation. Requires BOTH the confirmation number AND an email that matches the reservation (renter or cardholder). Returns customer-facing details only: status, vehicle, pickup/return dates, locations, and totals. Use this to answer 'what are my dates / where do I pick up / what did I book'. For changing or cancelling, point the customer to the VIP program. Does NOT expose internal notes or staff fields — use lookup_reservation (admin) for full staff detail.
    ConnectorNo auth
  • Fuzzy-match a vehicle by make (and optional model/year) to confirm it exists and correct spelling before a plan search. Use this when the user's make/model looks misspelled or uncertain.
    ConnectorNo auth
  • Wallet token balances (SOL + all SPL tokens) with USD valuations. detail="concise" (default) returns total_usd + count + balances trimmed to token/symbol/usd_value (IDs for chaining into e.g. get_quotes); "full" returns every field (amount, price_usd) as before. Workflow: ORIENT step -- the starting read for any flow. See get_trading_workflow.
    ConnectorNo auth