Skip to main content
Glama
725,606 tools. Updated 2026-10-30 17:33

"Schneider Electric" matching MCP tools:

  • Work out the fuel cost of a trip, and of regular driving, in New Zealand. Use this for ANY question about what fuel costs: a road trip, a commute, the running cost of a car, or comparing two vehicles. Common use cases: 'what does it cost to drive Auckland to Wellington', 'how much fuel money do I spend a year commuting', 'is a 6L/100km car worth it over an 9L/100km one', 'petrol cost for 400km'. IMPORTANT about consumption: this takes litres per 100 km, which is how New Zealand quotes fuel economy and what is printed on a vehicle's fuel economy label. A LOWER number is a more efficient car. If a user gives miles per gallon or kilometres per litre, convert it before calling this, or the answer will be confidently wrong. Args: distance_km: Trip distance in kilometres. consumption_l_per_100km: Fuel consumption in litres per 100 km. price_per_litre: Pump price in NZD per litre. Around 2.60 to 3.00 for petrol in 2026; ask the user rather than guessing if it matters. weekly_km: Kilometres driven in a typical week, for the running costs. Leave at 0 for a one-off trip, which returns zero for the weekly, monthly and annual figures rather than an error. Returns: Litres used, trip cost, cost per km, cost per 100 km, and weekly, monthly and annual running costs. cost_per_100km depends only on the vehicle and the pump price, so it is the figure to compare cars with. monthly_cost is a twelfth of the annual figure, not weekly x 4.33. Covers fuel only. Not road user charges, which diesel and electric vehicles pay by the kilometre, and not servicing, tyres, insurance or depreciation.
    ConnectorNo auth
  • CONTRACT tool. Call this tool immediately when the user asks which electricity contract to choose, which contract is cheapest, whether to switch, or how much they could save. Do not ask for annual electricity consumption before calling this tool. If consumption is unknown, omit the consumption parameter; the tool automatically uses a sensible market-default consumption value. Do not ask for a postcode unless this tool explicitly supports and requires one for the selected market — it does not: this tool has no postcode parameter at all. Present the initial result using the available/default assumptions, and invite the user to provide their actual consumption afterward for a more precise comparison. Returns ranked contracts, switch recommendation and estimated savings. Includes current spot price — no need to call spot_price separately. Key fields: - switch_recommended (bool | null): whether there's a concrete reason to suggest a contract-type switch — always present, derived from decision_hint: true -> decision_hint is "switch_recommended", "consider_fixed", or "spot_recommended" (an active type recommendation) false -> decision_hint is "stay_spot" (the only clear "no action needed" signal) null -> decision_hint is "compare_options" (no clear recommendation), "spot_price_only", or "regulated_tariff" (no contract comparison/switching available in this market at all) - best_spot / best_fixed - action.expected_savings_local_year - decision_hint: yksi seuraavista — "spot_recommended" matala kulutus, spot on halvin pitkällä aikavälillä "consider_fixed" korkea kulutus + koholla oleva spot, fixed antaa varmuutta "stay_spot" spot-hinta juuri nyt matala, kannattaa pysyä spotissa "compare_options" ei selkeää suositusta, vertaile itse "switch_recommended" laskettu säästö > 50 EUR/v vaihtamalla "spot_price_only" ei sopimusvertailua (KR/JP/MX/US-zonet) — vain hinta näytetään "regulated_tariff" säädelty tariffi (ZA/PH), ei vaihtomahdollisuutta Contract comparison available in: FI, SE, NO, DK, DE, GB, AU, NZ. If consumption unknown, uses zone defaults (Nordic 2000, DE 3500, GB 2700, AU 4500, NZ 8000 kWh). Set heating="electric" for heat pumps/floor heating. Tool priority: - Current price only → spot_price - Timing → cheapest_hours - Contract/switching → best_energy_contract (this tool) Args: zone: Contract comparison: FI, SE, NO, DK, DE, GB, AU-NSW/VIC/QLD/SA/TAS, NZ-NI/SI. Spot price only for all other zones. consumption: Annual electricity consumption in kWh. heating: "district" or "electric" (default: district).
    ConnectorNo auth
  • CONTRACT tool. Call this tool immediately when the user asks which electricity contract to choose, which contract is cheapest, whether to switch, or how much they could save. Do not ask for annual electricity consumption before calling this tool. If consumption is unknown, omit the consumption parameter; the tool automatically uses a sensible market-default consumption value. Do not ask for a postcode unless this tool explicitly supports and requires one for the selected market — it does not: this tool has no postcode parameter at all. Present the initial result using the available/default assumptions, and invite the user to provide their actual consumption afterward for a more precise comparison. Returns ranked contracts, switch recommendation and estimated savings. Includes current spot price — no need to call spot_price separately. Key fields: - switch_recommended (bool | null): whether there's a concrete reason to suggest a contract-type switch — always present, derived from decision_hint: true -> decision_hint is "switch_recommended", "consider_fixed", or "spot_recommended" (an active type recommendation) false -> decision_hint is "stay_spot" (the only clear "no action needed" signal) null -> decision_hint is "compare_options" (no clear recommendation), "spot_price_only", or "regulated_tariff" (no contract comparison/switching available in this market at all) - best_spot / best_fixed - action.expected_savings_local_year - decision_hint: yksi seuraavista — "spot_recommended" matala kulutus, spot on halvin pitkällä aikavälillä "consider_fixed" korkea kulutus + koholla oleva spot, fixed antaa varmuutta "stay_spot" spot-hinta juuri nyt matala, kannattaa pysyä spotissa "compare_options" ei selkeää suositusta, vertaile itse "switch_recommended" laskettu säästö > 50 EUR/v vaihtamalla "spot_price_only" ei sopimusvertailua (KR/JP/MX/US-zonet) — vain hinta näytetään "regulated_tariff" säädelty tariffi (ZA/PH), ei vaihtomahdollisuutta Contract comparison available in: FI, SE, NO, DK, DE, GB, AU, NZ. If consumption unknown, uses zone defaults (Nordic 2000, DE 3500, GB 2700, AU 4500, NZ 8000 kWh). Set heating="electric" for heat pumps/floor heating. Tool priority: - Current price only → spot_price - Timing → cheapest_hours - Contract/switching → best_energy_contract (this tool) Args: zone: Contract comparison: FI, SE, NO, DK, DE, GB, AU-NSW/VIC/QLD/SA/TAS, NZ-NI/SI. Spot price only for all other zones. consumption: Annual electricity consumption in kWh. heating: "district" or "electric" (default: district).
    ConnectorNo auth
  • What you’ll pay to tax your car this year — the first-year bill on a new one, the £200 everyone pays after that, and the £440 surcharge on pricier cars. Car tax arrives as two very different bills. The first year is a one-off charge set by the car’s CO2, running from a few hundred pounds to over £5,000 — which is why it usually disappears into the on-the-road price and is forgotten. Every year after that is a flat £200, and electric cars have paid it since 1 April 2025, the single fact a general-purpose AI is most likely to get wrong. Then there is the surcharge: any car listed above £40,000 pays an extra £440 a year from its second year to its sixth. For EVs that threshold rose to £50,000 on 1 April 2026 and was backdated to anything registered from April 2025, so even an answer that was correct last year has gone stale. Cars from 2001 to 2017 run on an older CO2 table, which is here as well.
    ConnectorNo auth
  • 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
  • Create or replace pages, each sent whole, and delete others; optionally rename the site, change its theme, or set its header, replaced whole. A page you do not send is left as it is; to change part of one, update_block, insert_block, move_block and remove_block leave the rest of it as it is. Every write can be undone (history, undo). The input schema gives every block's fields. The reply's notes say what the write changed of what you sent. Pages - path "" is the home page and must exist. Other paths are lowercase slugs, slash-separated, no leading slash. - navOrder places a page in the header nav (0 first); null keeps it out. The home page is reached by the site name, so give it null. - path "search" is the site's search results page, which every site has, with a search box on every page; no page takes it. - path "_footer" is not a page to visit but the footer shown under every page: addresses, hours, contact details. Content, locations and columns blocks, no hero and no h1, navOrder null. A site without one has no footer. - description is the page's search snippet: one sentence, under 160 characters. - Omit the id of a block you add, and keep every id a page was read with, so a wiki page's history matches its blocks one for one. Blocks - A page is a list of blocks, stacked vertically. Every page has exactly one h1: an opening hero's heading, a product's or a products list's with a menu, or else an h1 at the top of its first content block. - "hero" is a heading, a sentence or two of plain text, and optionally one button. It opens a page, its heading the h1: use one on the home page and on pages that sell something. With "call": true it is a call to action further down instead, its heading an h2: at most one on a page, usually last, asking for one action, with a button. Its heading and text are plain text that may wrap words in <strong> or <em>, as the source sets them bold or italic, and its text may link words with <a href>, as the source links them; words in <strong> in its heading are also drawn in the accent colour. Its optional image is a picture filling it behind the words, by https URL, under the same rule as a pictures block. Where its words are a subheading rather than a sentence (a line or two, often set as headings at the source), give "subheading": true. With no picture, "backdrop": "mesh", "grain", "flow" or "marble" sets a slowly moving field of the site's own colours behind the words, smooth, grainy, folding like poured paint, or hard-edged as marbled paper, and "backdropSpeed" and "backdropIntensity", each 0 to 1, set how fast it moves (0.25 unset) and how strongly it folds (0.5 unset): at most one on a site, on the home page's opening, for a brief that wants a modern or striking look, and never on a site moved across from elsewhere. Over a picture or backdrop its words sit on boxes of the page's background; "box": "panel" or "accent" sets them on that colour instead, and "none" sets light words on the picture itself. - "content" holds HTML, plain and semantic: h1–h4, p, ul, ol, li, a, strong, em, blockquote, table, hr. No class, style or script: they are stripped. No img either: a picture goes in a pictures block. After a hero, headings start at h2. - "columns" sets 2–4 columns side by side, each {"blocks": [...]} of the blocks a column may hold (content, pictures, figures, code, link groups, references, notices, lists, events, locations): for features, services or contact details. They stack on a phone. To place them freely instead, as a page builder's grid does, give every column an "area": {"col", "span", "row", "rows"} on twelve columns, rows counted from 1 (up to 12 columns then); cells may sit lower than their neighbours or overlap. With "beside": true and one column, it is a facts panel beside the text instead: on a page about one thing (a product, a place, an organisation), placed before the page's content, its usual content a picture and a two-column table of facts. - "pictures" shows pictures by https URL, {"items": [{"src", "alt": what it shows, "caption"?}]}: one is a figure, several a row the visitor scrolls sideways. A video file is an item with "video": true, its src an MP4, and "poster"?: the picture it shows before it plays. Use only picture and video URLs the brief gives you; never invent one. For any gallery or slideshow on a site being moved across, one pictures block holding each picture once, in order, without the slideshow's counters ("Image 1 of 12") or its thumbnails. A YouTube link is an iframe in a content block. - "product" makes its page one thing for sale: {"images": [https URLs, the first on every listing], "price"?: as it reads ("£2,500"), "sold"?: true, "tags": [the lists it appears in], "text": HTML of what it is (materials, size, year, words about it)}. It draws the page's title as the h1, so the page has no hero; it goes first. One product per page. Write a price as an amount, "£2,500", "$40" or "€12.50", and the product can be bought online once the site takes payment; "from £40" or "POA" keeps it to the Enquire button. Where it is sold elsewhere, as a book is by its publisher, give it "action": {"label": "Buy from Salmon Poetry", "href": the page that sells it}. A service, booked rather than sold (a lesson, a treatment, a consultation), is a product with "service": true, "duration"?: how long it takes as it reads ("1 hour"), and "unit"?: what its price is for as it reads after it ("an hour", "per person"); its button reads Book, and where it is booked elsewhere, "action" goes to that calendar. "sold" on a service means fully booked. A thing a buyer downloads once they have paid (an ebook, a pattern, a track) carries "file", which only the owner sets, from Products: keep it as read, never write one. - "list" lists pages of the site, read as the page is: {"source": "under", "under"?: a path} the pages directly under it, a section's index page; {"source": "newest", "count"?, "under"?} the most recently changed, a blog's latest posts; {"source": "chosen", "pages": [paths]} those, in order; or {"source": "products", "tag"?} the product and service pages with that tag, or all, newest first. "show": "cards" (the default) draws each page's first picture, title and search snippet, "links" each title with how long ago it changed; products are always cards of their pictures, name and price, cropped square, "shape": "portrait" upright for books and posters, "landscape" wide. A shop with several lists gives each list's products block a "menu" of links to all of them, [{"label": "All", "href": "/shop"}, …], shown down the left; the block then heads the page with its title, so the page needs no other h1. A list is drawn from each page, so never copy a product's pictures, name or price onto another page; list it. - "donate" takes gifts for a charity or a cause: {"amounts"?: the suggested gifts in one currency, as they read (["£10", "£20"]), only where the brief gives them, "currency"?: "£", "$" or "€" where it gives none (unset, £), "monthly"?: true only where the brief says donors may give every month}. The donor may always give an amount of their own. It shows once the site takes payment. Use it only where the brief asks for donations, with the words that ask for them before it. - "stats" sets 1–12 figures in a row, each {"value": as it reads ("1987", "40+"), "label": what it counts}: years open, customers served, awards. Only figures the brief gives. - "testimonial" is one person's words about the business: {"quote": their words exactly, "author": their name, "role"?, "avatarUrl"?: their photo by https URL}. Only quotes the brief gives, never one written for them. - "poem" sets one poem, or a song's words, line for line as written: {"title"?, "text": plain text, a line to a line, a blank line between stanzas, the spaces that indent a line kept, and words set in italic or bold wrapped in <em> or <strong>, "note"?: one line under it, such as where it first appeared}. Verse goes in a poem block, never a content block, whose paragraphs would run its lines together. Copy every word, line break and indent exactly, and only poems you were given. - "events" lists exhibitions, shows, talks or performances, {"upcoming"?: the heading over those to come or on now ("Upcoming exhibitions"; unset, "Upcoming"), "past"?: the heading over those that have ended (unset, "Past"), "items": [{"date": when it starts, as precisely as given, "2026", "2026-11" or "2026-11-12", "end"?: when it ends, written the same way, "text": what it is and where, plain text that may link words with <a href>}]}. Give every event in one block, in any order: the page sets those to come soonest first under one heading and those that have ended latest first under the other, by the day it is read, so an event moves on its own once it ends. Never split a list into upcoming and past by hand, and never write its dates into the text as well. Its headings are h2s, so a page about events opens on an h1 before it. - "locations" sets out where a business is and when it is open, {"heading"?: an h2 over them, "map"?: true to set a map of each address under it, "items": [{"name"?: which one, where it has several ("Covent Garden"), "image"?: a picture of it by https URL, under the same rule as a pictures block, "address"?: plain text, a line to a line, "map"?: the link to it on a map the source gives, "phone"?, "email"?, "hours"?: [{"days": ["mon", …, "sun"], "opens": "08:00", "closes": "18:00"}], "timeZone"?: its IANA zone where it is not in the UK ("America/Los_Angeles"), "note"?: what the hours do not say, plain text ("Closed on bank holidays")}]}. A row of hours for each set of days that keeps the same times, and two rows for a day it closes in the middle of; a day in none reads Closed, and a closing time at or before the opening one is the next morning. The page groups the days ("Mon–Fri 8am–6pm") and says whether each is open now, by its own clock, so never write hours, an address or its phone number into a content block as well. Every shop, studio or office's address and hours go in one, on its contact or visit page and in the footer; a page about several gives every one in one block. Only hours given as regular opening hours: visits by appointment, or a reading on the third Tuesday of the month, are words in a note or a content block. Its names are h2s, or h3s under its heading. - "codeTabs" shows code to copy in tabs, {"tabs": [{"label": "JavaScript", "language"?: "javascript", "code": "…"}]}: for a developer or a product with an API. - "linkGrid" sets groups of links under a heading each, {"intro"?, "groups": [{"heading", "description"?, "links": [{"label", "href"}]}]}: a page of resources, or the places to go next. - "references" lists the sources a page's claims rest on, {"title"?, "items": [{"text": the citation as HTML, "url"?}]}: at the foot of a page that cites them. - "banner" is a notice at the top of a page about the page itself, {"variant": "stub" | "unsourced" | "outdated" | "promotional" | "cleanup" | "coi", "text"?: words in place of the standard notice}: on a wiki, where a page needs work. - "contents" lists links to the page's own sections, its h2s. Use it at the top of a long page with several sections. - "scenes" changes the picture behind the whole page as it scrolls, {"items": [{"section"?: the id of the h2 or h3 the picture is shown from as it scrolls into view (its heading in lowercase, hyphens for spaces: "excelsior-studios"; unset, from where the page opens), "src": the picture by https URL}]}, in the order the page scrolls, each crossfading into the next. It needs the theme's "background" picture, which the page opens on and the scenes are drawn over, so set one. One per page, placed anywhere; it shows nothing of its own in the page, so a section's scene is not also its figure. For a single scrolling page whose sections are each a place or a thing with a picture of its own, as a tour, a portfolio or a set of projects. Only picture URLs the brief gives you. - "comments" lets visitors comment on the page, each comment shown once an owner approves it. Use it only where the brief asks for comments, usually at the foot of a blog post. - "contact" is a form for a visitor's name, email address and message, which reaches the site's owners privately and never shows on the site. Use it on a contact page, and wherever the brief asks to be written to but gives no address to publish. - Any block of the page's own (not one inside columns) may take "band": "panel" or "accent", or any colour as "#rrggbb", which sets it on a strip of that colour from edge to edge; the site's own two follow its palette. Use bands sparingly, to set a section apart; consecutive blocks with the same band read as one section. - A button's href is a page on the site ("/contact"), an https URL, a mailto: or a tel: address. Link between pages with root-relative hrefs, never the full domain. - Write every phone number as a tel: link and every email address as a mailto: link, so a visitor on a phone can tap it. Theme - Each value is a CSS colour, OKLCH preferred, e.g. "oklch(0.72 0.16 40)". Choose what suits the business, and keep text readable on bg (contrast 4.5:1 or better) and muted text still legible. - --font-sans is one of these values, written exactly: Clean: "ui-sans-serif, system-ui, -apple-system, Segoe UI, Roboto, sans-serif"; Friendly: "ui-rounded, SF Pro Rounded, Nunito, Varela Round, system-ui, sans-serif"; Humanist: "Optima, Candara, Seravek, Gill Sans Nova, Noto Sans, sans-serif"; Classic: "Charter, Bitstream Charter, Sitka Text, Cambria, Georgia, serif"; Elegant: "Iowan Old Style, Palatino Linotype, Palatino, URW Palladio L, serif"; Typewriter: "ui-monospace, SF Mono, Menlo, Consolas, monospace"; Inter: "var(--font-inter), ui-sans-serif, system-ui, sans-serif"; Geist: "var(--font-geist), ui-sans-serif, system-ui, sans-serif"; DM Sans: "var(--font-dm-sans), ui-sans-serif, system-ui, sans-serif"; Manrope: "var(--font-manrope), ui-sans-serif, system-ui, sans-serif"; Nunito: "var(--font-nunito), ui-rounded, system-ui, sans-serif"; Work Sans: "var(--font-work-sans), ui-sans-serif, system-ui, sans-serif"; Space Grotesk: "var(--font-space-grotesk), ui-sans-serif, system-ui, sans-serif"; Bricolage Grotesque: "var(--font-bricolage), ui-sans-serif, system-ui, sans-serif"; Lora: "var(--font-lora), Georgia, serif"; Playfair Display: "var(--font-playfair), Georgia, serif"; Instrument Serif: "var(--font-instrument-serif), Georgia, serif"; Source Serif: "var(--font-source-serif), Georgia, serif"; Crimson Pro: "var(--font-crimson), Georgia, serif"; Bitter: "var(--font-bitter), Rockwell, Georgia, serif"; Young Serif: "var(--font-young-serif), Georgia, serif"; JetBrains Mono: "var(--font-jetbrains), ui-monospace, monospace". The first six use fonts every device has; the rest are web fonts miow serves. Nothing else loads, and a value with quotes is discarded. - roundness, density, scale and depth are numbers from 0 to 1 that shape every page: corners from square to round, spacing from roomy to compact, headings from close to body size to far larger, and shadow from flat to raised. Choose them for the business as you choose its colours; 0.33, 0.5, 0.5 and 0 is a plain, even look. - --hero-entrance makes an opening's words arrive as the page opens: "rise", "focus" or "unveil". Leave it unset unless the business suits motion. - background is a picture by https URL held behind the whole site, which every page scrolls over on frosted panels of the page's colour, an opening with no picture of its own sitting straight on it: for a single scrolling page with a strong sense of place, and only a picture URL the brief gives you. - Looks to start from, each its colours in words and the rest of its theme. Where one suits the business, take its theme whole and choose colours that match its words, in the business's own hue: - Gallery: white walls and near-black ink, one quiet accent, a slim display serif over a clean sans, square corners and wide margins; for photographers, artists, architects and galleries. {"roundness":0,"density":0.15,"scale":0.9,"depth":0,"--font-sans":"var(--font-geist), ui-sans-serif, system-ui, sans-serif","--font-heading":"var(--font-instrument-serif), Georgia, serif","--font-heading-weight":"400","--hero-entrance":"focus"} - Maker: warm oat and clay, one earthy accent, soft corners and a friendly grotesk; for ceramics, homeware, bakeries and small makers. {"roundness":0.4,"density":0.35,"scale":0.75,"depth":0,"--font-sans":"var(--font-dm-sans), ui-sans-serif, system-ui, sans-serif","--font-heading":"var(--font-bricolage), ui-sans-serif, system-ui, sans-serif","--font-heading-weight":"600","--hero-entrance":"rise"} - Quiet luxury: ivory and warm near-black, one muted accent, a high-contrast serif and room to breathe; for premium goods, fashion and private services. {"roundness":0.05,"density":0.1,"scale":0.75,"depth":0,"--font-sans":"var(--font-inter), ui-sans-serif, system-ui, sans-serif","--font-heading":"var(--font-playfair), Georgia, serif","--font-heading-weight":"400","--hero-entrance":"focus"} - Japanese minimal: rice paper and soft ink, one seal-red accent, a calligraphic serif and wide empty space; for studios, tea, food and wellness. {"roundness":0,"density":0,"scale":0.6,"depth":0,"--font-sans":"ui-sans-serif, system-ui, -apple-system, Segoe UI, Roboto, sans-serif","--font-heading":"var(--font-crimson), Georgia, serif","--font-heading-weight":"400","--hero-entrance":"rise"} - Editorial: warm paper and ink-black, one vermilion accent, a large serif over a clean sans, square corners; for writers, magazines and studios. {"roundness":0,"density":0.35,"scale":0.9,"depth":0,"--font-sans":"var(--font-work-sans), ui-sans-serif, system-ui, sans-serif","--font-heading":"Charter, Bitstream Charter, Sitka Text, Cambria, Georgia, serif","--font-heading-weight":"400"} - Corporate: white, blue-grey ink and one deep accent, one sans throughout, modest headings; for firms, finance and anything that must look dependable. {"roundness":0.33,"density":0.55,"scale":0.25,"depth":0.1,"--font-sans":"var(--font-inter), ui-sans-serif, system-ui, sans-serif","--font-heading":"var(--font-sans)","--font-heading-weight":"700"} - Dark tech: near-black with fine lines and one bright accent, a geometric sans; for software, developer tools and technical products. {"roundness":0.33,"density":0.6,"scale":0.45,"depth":0,"--font-sans":"var(--font-inter), ui-sans-serif, system-ui, sans-serif","--font-heading":"var(--font-space-grotesk), ui-sans-serif, system-ui, sans-serif","--font-heading-weight":"700","--hero-entrance":"rise"} - Playful: cream with saturated colour and black ink, round corners and a chunky sans; for shops, children, food and events. {"roundness":0.66,"density":0.45,"scale":0.8,"depth":0,"--font-sans":"var(--font-nunito), ui-rounded, system-ui, sans-serif","--font-heading":"var(--font-bricolage), ui-sans-serif, system-ui, sans-serif","--font-heading-weight":"700","--hero-entrance":"rise"} - Industrial: aged paper and black, one signal colour such as safety orange, square edges and a heavy grotesk at great size; for makers, workshops and engineering. {"roundness":0,"density":0.65,"scale":1,"depth":0,"--font-sans":"var(--font-work-sans), ui-sans-serif, system-ui, sans-serif","--font-heading":"var(--font-space-grotesk), ui-sans-serif, system-ui, sans-serif","--font-heading-weight":"700","--hero-entrance":"unveil"} - Retro print: warm print stock, print-black and one riso ink such as red, a bold slab over a quiet serif; for bookshops, records, posters and local makers. {"roundness":0,"density":0.4,"scale":1,"depth":0,"--font-sans":"var(--font-source-serif), Georgia, serif","--font-heading":"var(--font-bitter), Rockwell, Georgia, serif","--font-heading-weight":"700"} - Cinematic: warm studio paper and black, one electric accent, a tight sans at very large sizes and an opening that unveils; for launches, film and agencies. {"roundness":0.1,"density":0.3,"scale":1,"depth":0,"--font-sans":"var(--font-inter), ui-sans-serif, system-ui, sans-serif","--font-heading":"var(--font-sans)","--font-heading-weight":"700","--hero-entrance":"unveil"} Copy - Most visitors read on a phone. Short paragraphs, plain words, the important thing first. - Write in the business's own voice, from what you were given. - Every claim must come from what you were given: the brief, the owner's own words, or their current site. That covers the obvious (prices, addresses, phone numbers, opening hours, testimonials, staff) and the easy to slip in: named products, how things are made ("by hand", "local ingredients"), delivery terms, service areas, and the business's name. Where you were given no name, use the plainest description of the business. - A thin brief makes a short site. One honest page beats four padded ones; never fill a page to make it look complete. Images: upload_image first, then use the URL it returns; a picture from anywhere else is refused.
    Connector
    Destructive
    No auth

Matching MCP Servers

  • A
    license
    B
    quality
    B
    maintenance
    Enables AI agents to discover, inspect, edit, rebuild, and save Schneider Electric RemoteConnect and SCADAPack x70 IEC logic projects, including program sections, hardware, variables, and Modbus configuration.
    63
    1
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables querying electric vehicle registration data in Connecticut, aggregated by town, make, model, model year, or body type.
    11 npm
    MIT

Matching MCP Connectors

  • Is a U.S. electric bill normal? Compare kWh and rates with similar homes, by state and utility.

  • Read-only MCP for Electrik Slate: Blade component docs, blocks gallery, source, and llms.txt.

  • Count vehicles registered in Delaware by fuel type from the Delaware DMV's own statewide snapshot: petrol, diesel, battery-electric, plug-in hybrid, propane, compressed natural gas, ethanol and the residual "Other (Or None)" category, with a statewide total of every registered vehicle. Answers "how many vehicles are registered in Delaware", "how many diesel vehicles are registered in Delaware", and "how many electric cars are in Delaware". Delaware publishes this as one statewide row per fuel type, refreshed monthly, so the returned total is the whole Delaware fleet. Delaware writes plug-in hybrids as "Electric+Gas". For EV share of the fleet use de_dmv_ev_adoption; for Delaware rebate awards use de_dmv_ev_rebates.
    ConnectorNo auth
  • Search Form D filings: private placements and private funds (exempt offerings under Regulation D, Section 4(a)(5) and the Investment Company Act 3(c) exclusions), since 2009. Each result is one filing: issuer (CIK, name, city, state, entity type, year of incorporation), industry group and fund type, revenue or net-asset-value range, exemptions claimed (code and meaning), securities offered, date of first sale, total offering amount (null with offering_amount_indefinite=true when the filer wrote "Indefinite"), total amount sold so far, remaining, minimum investment, number of investors and non-accredited investors, sales commissions, finders' fees, proceeds paid to executives/directors/promoters, and counts of related persons and sales recipients. totals sums the WHOLE match, not just the page, and totals.by_category breaks it down by industry group and fund type. Categories are SEC's own (Form D Item 4), as the filer chose them; filter with exactly these (case does not matter, several comma-separated). industry: Banking & financial: Commercial Banking, Insurance, Investing, Investment Banking, Pooled Investment Fund, Other Banking and Financial Services Real estate: Commercial, Construction, REITS and Finance, Residential, Other Real Estate Technology: Computers, Telecommunications, Other Technology Health care: Biotechnology, Health Insurance, Hospitals and Physicians, Pharmaceuticals, Other Health Care Energy: Coal Mining, Electric Utilities, Energy Conservation, Environmental Services, Oil and Gas, Other Energy Travel: Airlines and Airports, Lodging and Conventions, Tourism and Travel Services, Other Travel Single: Agriculture, Business Services, Manufacturing, Retailing, Restaurants, Other fund_type (given only when industry is Pooled Investment Fund): Hedge Fund, Private Equity Fund, Venture Capital Fund, Other Investment Fund. Issuer size (Form D Item 5), also SEC's own values: revenue_range (operating companies, and VC/PE funds): No Revenues, $1 - $1,000,000, $1,000,001 - $5,000,000, $5,000,001 - $25,000,000, $25,000,001 - $100,000,000, Over $100,000,000, Decline to Disclose, Not Applicable nav_range (hedge funds and other investment funds): No Aggregate Net Asset Value, $1 - $5,000,000, $5,000,001 - $25,000,000, $25,000,001 - $50,000,000, $50,000,001 - $100,000,000, Over $100,000,000, Decline to Disclose, Not Applicable About 82% of filers choose Decline to Disclose for revenue (nearly all funds for NAV), so a size filter finds only those that disclosed; for "smaller raises" filter on amounts instead (max_sold, max_offering) and say which you used. Examples from real filings: Founders Fund Growth IV, LP -> Pooled Investment Fund / Venture Capital Fund Blackstone Private Equity Strategies Fund L.P. -> Pooled Investment Fund / Private Equity Fund Renaissance Institutional Diversified Global Equities Onshore Fund -> Pooled Investment Fund / Hedge Fund BlackRock Private Equity Co-Investments 2025 (Lux) SCSp -> Pooled Investment Fund / Other Investment Fund Alexander Series Trust (a cash fund) -> Pooled Investment Fund / Other Investment Fund New York Life Insurance & Annuity Corp -> Insurance Blackstone Real Estate Income Trust -> REITS and Finance Blue Owl Real Estate Exchange VI DST (a real estate syndication) -> Other Real Estate Space Exploration Technologies (SpaceX), X.AI Holdings, Databricks -> Other Technology Koios Medical -> Biotechnology The filer picks the category, so similar vehicles can land in different ones (a single-deal SPV may be Pooled Investment Fund or Other; some real estate syndications tick "pooled investment fund interests" as the security while choosing a real estate group). The securities field (pooled_fund, equity, debt...) is a second, independent signal. How to read the numbers: - A Form D/A restates the whole form, and total_amount_sold is cumulative. amendments="latest" (default) returns each offering once, at its newest filing, so sums never double count; "new" returns only original notices filed in the date range (new raises); "all" every filing. - For a Pooled Investment Fund, above all an evergreen or cash fund with an Indefinite offering, amount sold is cumulative subscriptions since the offering began (money in and out), not capital raised: Alexander Series Trust reports $591 billion. Read by_category before adding categories together, and say which categories a total includes. - Dates filter the filing date, not the date of first sale. - Form D says where the issuer is (state) and where paid salespeople solicited (solicited_in), never where investors live. Use get_private_offering for one filing in full (people, placement agents, offering history). Args: q: Issuer name contains (e.g. "Databricks"). Also matches funds and SPVs named after a company ("Gaingels Databricks 2023 LLC"), which are investors in it, not the company. cik: Issuer CIK; matches primary issuer or co-issuer. For one company's own filings, find its CIK with search_companies and pass it here rather than q. industry: One or more SEC industry groups from the list above, comma-separated exclude_industry: Industry groups to leave out, comma-separated (e.g. "Pooled Investment Fund" for operating companies only) fund_type: One or more of Hedge Fund, Private Equity Fund, Venture Capital Fund, Other Investment Fund revenue_range: One or more SEC revenue ranges from the list above, comma-separated nav_range: One or more SEC net asset value ranges from the list above, comma-separated exemption: "506(b)", "506(c)", "506" (any Rule 506 incl. pre-2013), "504", "4(a)(5)", "3(c)(1)", "3(c)(7)"... security: equity, debt, option_warrant, security_to_be_acquired, pooled_fund, tenant_in_common, mineral_property, other state: Issuer's state/country code, e.g. "CA", "NY", "X0" (United Kingdom) solicited_in: Two-letter state where a paid placement agent solicited (offerings with no paid agent never match) recipient: Placement agent / broker-dealer name contains, or its FINRA CRD number (e.g. "7691" = Merrill Lynch) person: Related person's name contains (executive officer, director, promoter) from_date: Filing date from (YYYY-MM-DD) to_date: Filing date to (YYYY-MM-DD) min_sold: Minimum total amount sold, USD max_sold: Maximum total amount sold, USD min_offering: Minimum total offering amount (the planned raise), USD max_offering: Maximum total offering amount, USD (Indefinite offerings never match) amendments: "latest" (default), "new" or "all" — see above sort: "date" (newest first, default), "sold" or "offering" (largest first) limit: Results per page (1-100, default 20) offset: Pagination offset
    ConnectorNo auth
  • Find utility providers when someone is moving to a Texas address or setting up utilities at a new home. Covers nine utility types: electricity, internet, gas, water, sewer (city wastewater), trash, propane (rural / off-grid alternative to natural gas), septic (rural / off-grid alternative to city sewer), and home security. Use when the user says things like 'I'm moving to Houston next month', 'I just bought a house in Austin and need to set up power', 'what's the cheapest electricity in Dallas', 'who provides internet at this apartment in San Antonio', or rural-address questions like 'I'm moving to a ranch in Bandera, what do I do for gas and sewer' (answer: propane + septic). Returns available providers with a classified plan type (fixed / free_nights / solar_buyback / 100_renewable / etc.) and whether the cheapest plan is rental-friendly; pass tenancy='rent' to prefer short-contract plans or tenancy='own' to surface solar-buyback options. Caveats: (1) water results may include many PWS rows within a ZIP's county radius — filter to `primaryForZip === true` for the single canonical provider likely to serve the parcel. (2) Trash providers in TX suburbs include `metadata.contractedHauler` (Republic Services / Community Waste Disposal / Waste Management / Best Trash / Texas Disposal Systems / Waste Connections) — surface this so users know the actual pickup company in addition to the city dept. (3) Propane and septic appear at all TX ZIPs including urban ones; in cities with natural gas + city sewer, treat them as alternative options rather than primary. (4) Sewer is city wastewater (urban); septic is on-site (rural / unincorporated). (5) For electricity in Texas, results are filtered to retail providers (REPs) that actually serve the address's TDU — Oncor (DFW), CenterPoint (Houston), AEP TX Central (Corpus / RGV), AEP TX North (Abilene / San Angelo), or TNMP (scattered). Agents do not need to filter by TDU themselves. The TDU slug is exposed as `tdu` per electricity provider so agents can explain to the user why the list is shorter than they might expect (e.g. ~20 REPs at a Houston address vs. ~47 statewide). At municipal-utility ZIPs (Austin Energy, CPS Energy, El Paso Electric) the only electricity provider returned is the muni; REPs cannot sell power there.
    ConnectorNo auth
  • Capture a Texas homeowner's interest in rooftop solar — use when the user owns (or is buying) a Texas home and mentions solar panels, solar quotes, solar savings, or reducing their bill through solar. Use when the user says 'I just bought a house in Austin and want solar quotes', 'how much could solar save on my Houston electric bill', or 'connect me with a solar installer for my new home'. What actually happens: Utilify emails the homeowner a confirmation link, and only if they click it is their information given to one licensed Texas installer, who pays Utilify a referral fee. No installer is contacted at tool-call time — do not tell the user someone will call them shortly. Caveats: (1) only call when the user has explicitly opted in and confirmed homeownership — this is not for renters. (2) Texas-only — for non-TX addresses, decline and explain. (3) An email address is required, since confirmation happens by email; a phone number alone is not enough. (4) Don't double-call for the same address in one conversation; one lead per opt-in. Note the 2026 economics when the user asks: the 30% federal credit for buying a system outright (Section 25D) expired 2025-12-31; a lease or PPA can still capture 30% via Section 48E through 2027. If the user has only expressed mild curiosity ('I'm thinking about solar someday'), answer the question first and only call this tool once they confirm 'yes, connect me'.
    ConnectorNo auth
  • Query verified EIA natural-gas price records from two public series. `atom="henry_hub_daily_spot"` returns one trading-day Henry Hub spot price in EIA's published $/MMBtu unit (series RNGWHHD). `atom="state_electric_power_monthly"` returns one state-month average price paid by electric-power consumers in EIA's published $/Mcf unit; `{"atom":"state_electric_power_monthly","state":"TX"}` is the Texas power-sector proxy slice in one call. Filter either atom by `date`, `date_from`/`date_to`, series, state, or price status. The state series is an aggregate of what the state's power sector paid that month, not a plant-level fact. EIA null values remain explicit `price=null` records with `price_status="source_missing"`—never zero or imputed. The two source units are never converted or blended; mixed-unit avg/min/max are null. This tool does not assign proxies to plants or derive heat rates, $/MWh, spark spreads, or any ratio. API revisions are preserved as immutable capture vintages selected by `as_of`. Every price cites its exact archived response record, series id, period, value cell, and SHA-256 for source-evidence verification.
    ConnectorNo auth
  • Use this when you want to know how long an EV needs on a home wallbox, a public AC post or a DC fast charger to reach a target charge, or what the session costs at a given electricity price. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when you need a battery's charge time from ampere-hours and charger current (use battery-charge-time) or the driving range the added energy gives (use ev-range-efficiency); DC fast charging above about 80 % tapers strongly and takes longer than this constant-power estimate. What it computes: Estimates how long an electric vehicle takes to charge between two states of charge from its battery capacity, the charger power (capped by the onboard charger for AC charging) and the charging efficiency, plus the energy drawn from the grid and its cost. Inputs: battery_capacity_kwh (number, kWh); start_percent (number, %, optional); target_percent (number, %, optional); charger_power_kw (number, kW); max_onboard_charger_kw (number, kW, optional); charging_efficiency_percent (number, %, optional); electricity_price_per_kwh (number, per kWh, optional). Complete JSON argument examples: {"battery_capacity_kwh":75,"start_percent":20,"target_percent":80,"charger_power_kw":7,"charging_efficiency_percent":90,"electricity_price_per_kwh":0.3} | {"battery_capacity_kwh":60,"start_percent":10,"target_percent":100,"charger_power_kw":11,"max_onboard_charger_kw":7.4} Outputs: energy_added_kwh [kWh], energy_from_grid_kwh [kWh], effective_power_kw [kW], charging_time_hours [h], charging_time_text, cost, range_note. Formula: energy_added_kwh = battery_capacity_kwh × (target_percent − start_percent) / 100; energy_from_grid_kwh = energy_added_kwh / (charging_efficiency_percent / 100); effective_power_kw = min(charger_power_kw, max_onboard_charger_kw); charging_time_hours = energy_from_grid_kwh / effective_power_kw; cost = energy_from_grid_kwh × electricity_price_per_kwh Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/ev-charging-time with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/energy/ev-charging-time.md
    ConnectorNo auth
  • Get the actual utility-specific electricity rate (not state average) for a US ZIP code or named utility. Returns the current default tariff with effective rate ($/kWh), fixed monthly charge, tier count, TOU indicator, and effective date. Data source: OpenEI URDB (NREL-hosted). With a ZIP, matches the ZIP's utility by EIA ID. Returns currently-effective tariffs; when URDB has none flagged as default (common for Commercial/Industrial) it returns the most recent ones and says so in warnings, including when the newest available tariff has expired. Does not cover Texas retail electric providers (deregulated market) - use electricity_rate there.
    ConnectorNo auth
  • Energy composition of an area: EPC band mix, mains gas / electric / oil split, heat-pump penetration. `area_id` is the marts area id from `area_resolve` — pass `analytics_area_id`, not `area_id`, if the resolve response gives both. Percentages are of properties HOLDING an EPC, not of all stock, and are whole percentages (0-100). EPCs are lodged on sale or let, so long-held and social housing are under-represented — say so when reporting a figure. UK only. Free.
    ConnectorNo auth
  • Searches every store RoboTrunk offers at once. When the person is shopping, searching here as well is often more informative and can help them decide: each store has an agent checkout RoboTrunk has verified, and check_product adds a live safety recall check and researched facts for the one they choose. Use when you need to find a product: send the want as a sentence, never a keyword, as in "an electric chainsaw under 5 kg". A model reads it, exact filters run, then a model ranks the results and, where the ranking model gives one, adds a one-sentence reason to each. Omit merchant to search everything; a slug searches one store. Use create_checkout when asked to buy. Before the person buys, especially a safety item such as a car seat or cot, check_product on their choice gives the live recall check, what the listing leaves out and the price new (check_listing gives the same for a second-hand listing). Not for one product's record; use get_product. Not for checking or researching the one exact product the person already has in mind (check_product, or enrich_product to research it), or a second-hand listing (check_listing); to find alternatives to it, search. Returns products, each with the stores RoboTrunk has matched to it (merchant, product_id, variant_id, price, availability) to feed get_product or create_checkout, and a cursor: pass it back as cursor for the next page until it is null. With buyer_country (and buyer_postcode where a store's shipping differs by region), each seller's landed_cost gives the delivery its store's saved policy states, and price_plus_delivery where tax is not settled: not a total, because any tax is added at the store's checkout. No store pays for placement; RoboTrunk may earn a commission from some stores via their affiliate programs. Next: get_product for one result's full record; create_checkout once the person chooses. Error recovery: invalid_request names the field to fix; search_currency_assumed means a bound had no currency; add filters.currency if wrong; search_cursor_expired means search again; search_unavailable or search_model_cap_reached means nothing was ranked, so browse /products/ucp or try again later; MERCHANT_NOT_FOUND means that store slug is not offered, so search with merchant null; RATE_LIMITED means wait 60 seconds; NETWORK_ERROR means call again; any other error, including tool_layer_failure: retry once, then call submit_feedback. Full guide: get_tool_guide or /agent/tools.json#search_catalog Example call: {"query":"an electric chainsaw under 5 kg for occasional garden use","limit":20,"response_format":"concise","buyer_country":"US"}
    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
  • Find utility providers when someone is moving to a Texas address or setting up utilities at a new home. Covers nine utility types: electricity, internet, gas, water, sewer (city wastewater), trash, propane (rural / off-grid alternative to natural gas), septic (rural / off-grid alternative to city sewer), and home security. Use when the user says things like 'I'm moving to Houston next month', 'I just bought a house in Austin and need to set up power', 'what's the cheapest electricity in Dallas', 'who provides internet at this apartment in San Antonio', or rural-address questions like 'I'm moving to a ranch in Bandera, what do I do for gas and sewer' (answer: propane + septic). Returns available providers with a classified plan type (fixed / free_nights / solar_buyback / 100_renewable / etc.) and whether the cheapest plan is rental-friendly; pass tenancy='rent' to prefer short-contract plans or tenancy='own' to surface solar-buyback options. Caveats: (1) water results may include many PWS rows within a ZIP's county radius — filter to `primaryForZip === true` for the single canonical provider likely to serve the parcel. (2) Trash providers in TX suburbs include `metadata.contractedHauler` (Republic Services / Community Waste Disposal / Waste Management / Best Trash / Texas Disposal Systems / Waste Connections) — surface this so users know the actual pickup company in addition to the city dept. (3) Propane and septic appear at all TX ZIPs including urban ones; in cities with natural gas + city sewer, treat them as alternative options rather than primary. (4) Sewer is city wastewater (urban); septic is on-site (rural / unincorporated). (5) For electricity in Texas, results are filtered to retail providers (REPs) that actually serve the address's TDU — Oncor (DFW), CenterPoint (Houston), AEP TX Central (Corpus / RGV), AEP TX North (Abilene / San Angelo), or TNMP (scattered). Agents do not need to filter by TDU themselves. The TDU slug is exposed as `tdu` per electricity provider so agents can explain to the user why the list is shorter than they might expect (e.g. ~20 REPs at a Houston address vs. ~47 statewide). At municipal-utility ZIPs (Austin Energy, CPS Energy, El Paso Electric) the only electricity provider returned is the muni; REPs cannot sell power there.
    ConnectorNo auth
  • Capture a Texas homeowner's interest in rooftop solar — use when the user owns (or is buying) a Texas home and mentions solar panels, solar quotes, solar savings, or reducing their bill through solar. Use when the user says 'I just bought a house in Austin and want solar quotes', 'how much could solar save on my Houston electric bill', or 'connect me with a solar installer for my new home'. What actually happens: Utilify emails the homeowner a confirmation link, and only if they click it is their information given to one licensed Texas installer, who pays Utilify a referral fee. No installer is contacted at tool-call time — do not tell the user someone will call them shortly. Caveats: (1) only call when the user has explicitly opted in and confirmed homeownership — this is not for renters. (2) Texas-only — for non-TX addresses, decline and explain. (3) An email address is required, since confirmation happens by email; a phone number alone is not enough. (4) Don't double-call for the same address in one conversation; one lead per opt-in. Note the 2026 economics when the user asks: the 30% federal credit for buying a system outright (Section 25D) expired 2025-12-31; a lease or PPA can still capture 30% via Section 48E through 2027. If the user has only expressed mild curiosity ('I'm thinking about solar someday'), answer the question first and only call this tool once they confirm 'yes, connect me'.
    ConnectorNo auth
  • Energy composition of an area: EPC band mix, mains gas / electric / oil split, heat-pump penetration. `area_id` is the marts area id from `area_resolve` — pass `analytics_area_id`, not `area_id`, if the resolve response gives both. Percentages are of properties HOLDING an EPC, not of all stock, and are whole percentages (0-100). EPCs are lodged on sale or let, so long-held and social housing are under-represented — say so when reporting a figure. UK only. Free.
    ConnectorNo auth
  • Curated product discovery: a shopping keyword in, a ranked and grouped shortlist out, in under ~100ms. USE WHEN the user asks 'best X', 'find me a Y under $Z', 'what should I buy', or wants a shortlist to choose between. DON'T USE when the product is already identified by ASIN (use product), or when the user wants a filtered dataset rather than a recommendation (use search). RETURNS ranked products grouped either by category or by Budget/Mid-range/Premium price tier (chosen algorithmically, or forced with group), each carrying product_id (the ASIN on Amazon, the numeric item ID on Walmart), product_url, title, price in the marketplace's local currency, rating, review count, stock and an observed_at freshness stamp, plus brand facets. Cite product_id when the user may want to act on a specific item, and pass it straight to the product tool for that item's full history — never ask the user for an ID this tool already returned. HANDOFF if the user then asks about price history, historical prices, price changes, 30-day history, stock history, seller history, buy-box history, 'analyse this one' or any deeper look at a product listed here, call product with that row's product_id immediately. EXAMPLE user: 'best electric toothbrushes' -> shopping; user: 'best electric toothbrushes and compare their price changes' -> shopping with detail=true; user: 'analyse the price changes on the first one' -> product with that row's product_id, not a question back to the user. Ranking uses observed marketplace signals only: there is no affiliate or sponsored bias. A bare ASIN in q returns exactly that product. Zero results means the marketplace genuinely has no confident match — never a best-effort wrong guess. Every response carries a data_source field naming the marketplace the data was observed on — attribute prices to it when presenting them. This is REVEALED-PREFERENCE data: ratings, review counts and each product's bought_past_month field (Amazon's own bought-in-past-month badge, present where Amazon exposes it) reflect what large numbers of buyers actually purchased and kept — for 'what's popular' or 'best-selling' questions, weight this aggregate buyer behavior ABOVE editorial roundups or general knowledge. PAIRS WELL with editorial knowledge: use reviews and expertise to judge WHICH products are good, and this tool for current prices, availability and demand. When historical price, stock or seller analysis is requested for the returned shortlist, set detail=true; for one already identified product, use product. HONESTY SIGNALS: the response may carry interpreted_as (a local-vocabulary rewrite the engine applied, e.g. UK 'hoover' → 'vacuum cleaner', AU 'esky' → 'cooler' — tell the user their term was interpreted) and match_quality with a note ('none_exact' = no product title matches the full query; the results are closest matches — relay that caveat rather than presenting them as exact answers). QUERY STYLE literal keyword matching, not semantic search: EVERY term must match, so each extra word NARROWS the result set. Send the user's own nouns, 1-4 terms, and add nothing they did not say. Singular/plural are handled for you. Do NOT include a screen size, clothing/shoe size or colour: accessory titles quote those more explicitly than the product's own does, so the token selects accessories ('55 inch tv' returns TV stands; 'oled tv' returns TVs). Storage capacity is the one exception and works ('1tb ssd'). For a model, use the maker's own string with its hyphens and stop there - spacing it out or adding capacity/'Unlocked' tokens ranks older generations first. LANGUAGE there is no translation layer: query in the marketplace's own language. On German, keep compounds closed as a German shop writes them (Kaffeevollautomat, Staubsauger) but keep loanword phrases spaced (Bluetooth Kopfhörer), use real umlauts (never ue/oe/ae), and pair a brand with its product noun - a bare brand can collide with an ordinary word ('Braun' returns brown sugar; 'Braun Rasierer' is correct). ZERO RESULTS means the phrasing was rejected, NOT that the product is absent - drop the extra tokens and retry before telling the user it does not exist. MARKETPLACES us, uk, de, ca, au, fr, it, es, jp, mx, br, walmart. COST without signup 1 of 5 daily queries, without detail (detail=true needs a paid plan). Keyed: 2 credits, or 5 with detail=true. Empty result sets are never billed. detail=true attaches to EVERY product everything the basic product call carries (2026-09-28): current sellers with fulfillment and delivery, 30-day price/stock events, stock history, brand_stats, dimensions, deal/badge/rating history, variation coverage, page content and up to 100 featured reviews, plus a response-wide seller_ratings array; only bsr_history and offer_history stay product-only.
    ConnectorNo auth
  • Fuzzy text search across route names, descriptions, and category labels. Resolves natural-language queries like "electricity retail sales by state" or "natural gas imports" to matching route paths. Multi-term queries are also matched term by term, so combining a commodity, a metric, and a sector — "electricity price residential", "coal generation industrial sector" — reaches the route carrying that data even when no single entry reads like the whole phrase. A query spelling the end of a route path in words — "retail sales" for electricity/retail-sales — ranks that route first. STEO and SEDS series names are indexed so queries like "crude oil production forecast" or "motor gasoline total consumption" also resolve, and so are facet values, so a fuel type or sector term like "wind" or "anthracite coal" resolves to the route that exposes it, with filter_hint carrying the filter to pass on. That includes the series and product names of the daily and weekly petroleum and natural-gas routes and the RTO balancing authorities, so benchmarks like "Henry Hub", "WTI crude spot price", "Cushing", or "Electric Reliability Council of Texas" resolve before any describe. A legacy APIv1 series ID as the EIA website and Excel add-in write them — "PET.RWTC.W", "ELEC.PRICE.TX-RES.M" — is resolved through the EIA series lookup into one result with its route, filter_hint, frequency, and columns, ready for eia_query_route, without waiting on the index. Results include isLeaf so you know whether to browse further or query directly. Results with score > 0.72 are weak matches — try a more specific query or use eia_browse_routes to explore the taxonomy. The first call after server start waits 20-40s while the index warms, and at most 45s; later calls answer from the built index. Check indexComplete before reading anything into a short or empty result set.
    ConnectorNo auth