ConnectorNo auth
523,718 tools. Updated 2026-09-06 13:58
"Square" matching MCP tools:
- Compute square root, cube root, square, and cube of a number. Returns all four so callers don't have to call four tools.ConnectorNo auth
- Square Series: Series of square.ConnectorNo auth
- Square Wave: Square WaveConnectorNo auth
- Matrix Is Square: Matrix Is SquareConnectorNo auth
- Is Square Free: Is Square FreeConnectorNo auth
Matching MCP Servers
- AlicenseBqualityFmaintenanceA server that enables interaction with Square's API via Goose, supporting queries for locations, customers, and more with context preservation and MCP-compliant responses.124MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with Square's Connect API through the Model Context Protocol standard, allowing for operations like managing customers, processing payments, and handling inventory.32,288107Apache 2.0
Matching MCP Connectors
Indonesian-language public square for AI agents with daily limits and a public action ledger.
Search, draft and manage your podcast workspace from your agent.
- Chi Square Stat: Chi Square StatConnectorNo auth
- Generate a color harmony from a base color. base accepts a hex, CSS name, RNV brand name, or saved-palette reference (e.g. 'Spring line:2'). scheme is one of: complementary, analogous, triadic, split-complementary, tetradic (a.k.a. square), monochromatic, compound. Returns a list of hex colors. Read-only and deterministic: it derives the colors from the base and stores nothing, so it has no side effects and is safe to call repeatedly. Use to expand one base color into a related set; to blend existing colors into a single color use mix_colors, and to persist a set you like use save_palette.ConnectorNo auth
- Query verified U.S. private construction spending ($ millions) for data centers and semiconductor/computer-electronics manufacturing plants, from the U.S. Census Bureau's Value of Construction Put in Place (C30). Use this for "how much is being spent BUILDING data centers (or chip fabs) in the US" questions — the construction buildout in dollars, not capacity or investment. Filter by `category` ("data_center" — Census's named subcategory under Office; or "computer_electronic_electrical" — the semiconductor/computer-electronics manufacturing line under Manufacturing), `basis` ("seasonally_adjusted" = a seasonally-adjusted ANNUAL RATE, or "not_seasonally_adjusted" = the NOT-adjusted MONTHLY LEVEL), `data_month` (one month, ISO first-of-month e.g. "2026-04-01") or the `data_month_from`/`data_month_to` range, `year`, and `revision_status` ("preliminary", "revised", or "final"). Group by any of `category`, `basis`, `data_month`, `year`, or `revision_status`. Pass each parameter as a top-level key of `params` (flat — not nested under a `filter`, `filters`, or `where` key). Example: `{"category": "data_center", "basis": "seasonally_adjusted", "data_month": "2026-04-01"}` for one month; add `"group_by": ["data_month"]` over a `data_month_from`/`data_month_to` range for a series. Returns JSON aggregates with citations and optional row-level records when `include_records` is true — every value cites the exact Census workbook, sheet, row, and column. The two categories are DISTINCT series and are never conflated: `data_center` is data-center buildings; `computer_electronic_electrical` is the chip/electronics-manufacturing (fab) line — the CHIPS-Act build-out. `basis` is the other fork: the seasonally-adjusted series is an ANNUAL RATE (what the current monthly pace annualizes to), while the not-seasonally-adjusted series is the actual MONTHLY LEVEL. `revision_status` carries Census's own preliminary/revised/final marking verbatim. Data is monthly; the data-center series begins 2014-01. The response `as_of` is the release vintage (Census revises monthly); pin `as_of` to an earlier vintage to reproduce what was served then. NOT additive: `construction_spending_musd` is a published per-(category, basis, month) reading, so a total that mixes the two bases (an annual rate + a monthly level), or that sums the seasonally-adjusted ANNUAL-RATE series across months, is not a real figure — such a result carries a `construction_aggregation` scope note and ranking remainders omit the metric. Filter to one `basis` and `group_by data_month` for a series over time. Does not determine total data-center INVESTMENT (servers, chips, cooling, equipment — this is construction put-in-place only; Census does not publish an investment total), data-center MW capacity, count, square footage, or location (use the power.* capabilities for capacity and the interconnection queue), which company or project is building (Census C30 has no operator breakdown), public or government construction (this is PRIVATE construction only), or construction outside these two categories.ConnectorNo auth
- Get realized FX volatility for a currency pair, and size the FX risk on an exposure held to a future date. Computes 30-day and 90-day annualized volatility from historical ECB reference rates (standard deviation of daily log returns, annualized by sqrt(252)). Returns a qualitative bucket: LOW (<5%), MEDIUM (5-15%), HIGH (15-25%), VERY_HIGH (>25%), PEGGED (currency peg — near-zero volatility, e.g., USD/AED, USD/HKD). Also returns practical daily/weekly movement estimates and a settlement_risk_note explaining what the volatility means over a typical T+2 settlement period — use these to advise users on FX risk for their specific payment. PASS horizon_days WHENEVER THE USER'S EXPOSURE RUNS PAST SETTLEMENT. It returns a `horizon` block: the volatility scaled to that horizon as an actual rate band at 1 and 2 sigma, which end of the band hurts a payer versus a receiver, and what the band does and does not tell them about hedging. Use it for questions shaped like: - "should I hedge / lock in / take a forward for <future period>?" - "how far could <pair> move by <date>?" - "what rate should I budget for next year?" - "I have invoices in <currency> through 2027 — what is my risk?" - any exposure not settling within a few days. Count the calendar days from today to the date the exposure ends and pass that. Rough is fine — the band moves with the square root of time, so a month either way barely changes it. Read `sample_depth` before quoting any figure: this is REALISED volatility from a short history, not implied volatility, and the sample may be shorter than the horizon asked about (`horizon.beyond_sample`). Say so. IMPORTANT — the band is the range of FUTURE SPOT. It is not a rate anyone can transact at, and the width of the band is NOT the cost of a hedge. A forward is priced off the interest-rate differential between the two currencies, which we do not hold and must not guess or recall from memory. Relay `horizon.hedge_cost_note` rather than inventing forward points, a carry figure, or a "typical" hedging cost. Never state a forward rate. Args: base: Base currency (ISO 4217, e.g., "EUR") target: Target currency (ISO 4217, e.g., "TRY") horizon_days: Optional. Calendar days from today to the end of the exposure (1-1825). Omit for spot/settlement risk only. Examples: fx_volatility("EUR", "USD") fx_volatility("USD", "TRY") fx_volatility("GBP", "JPY", 506) # exposure running to end-2027 fx_volatility("EUR", "PLN", 90) # invoice settling in a quarterConnectorNo auth
- Configure this share — its name and its **appearance** — fields you don't pass stay as they are (server-side partial merge). - `label`: the name at the top of the chat page, and the browser tab's title. **Renaming a share is this call**; you never need to create a replacement and delete the old one. That would mint a new token, so the link already embedded in the client's site would stop working — the visible name and the address are not the same thing. - `theme_color`: the brand colour, `#RGB` or `#RRGGBB`. **This one colour is all you give** — its foregrounds are derived on save. - `highlight_color`: **only if the brand actually has a second colour.** Most don't; leave it out and nothing changes anywhere. When set, it is used where something should be visible without competing with the primary action: the second series in a chart, and citation markers. Buttons, the current storyline step and user bubbles stay on `theme_color` — two colours fighting over the same element is how a two-colour palette goes wrong. Foregrounds are derived from it the same way. Text/foreground colours are derived server-side to WCAG contrast and stored (a light brand colour automatically gets dark text instead of white) — **do not compute a palette yourself and do not try to set text colours**; they would be overridden. - `logo_url`: absolute URL. The header scales by height, any aspect ratio fits; **the collapsed launcher bubble is square**, so only near-square images (aspect 0.74–1.35) are used on the bubble — a wide wordmark falls back to the platform icon there. Want your mark in both places? Provide a square variant too. - `input_mode`: `text` (text box, default) or `voice` (opens in push-to-talk). Requires the platform's voice backend. - `launcher`: hover tooltip text for the bubble. `theme`: `light` / `dark` / empty = follow the visitor. - `custom_css`: the escape hatch for strict brand guidelines — the injected stylesheet can override our CSS variables (`--acc` / `--acc-fg` / `--acc-text-l` / `--acc-text-d` / `--bg` / `--surface` / `--text` / `--border`); write light values under `:root{…}` and dark under `html[data-theme="dark"]{…}`. **Prefer theme_color**: it carries a readability guarantee, with custom_css the contrast is on you. Get the token from `list_shares` first. Full examples in the Cookbook's configure-branding.ConnectorNo auth
- Build a location precisely from a scene-layout/v2 map and generate its plate. This is the "exact location building" path: instead of describing the room in prose (which the model reinterprets — furniture drifts, depths change between shots), it renders a control image from the map's boxes (each object a colored block at its true position/size/depth, plus a 1-meter floor grid in true perspective), then asks the generator to REPLACE each block with its real object in the same camera — so the plate follows the geometry pixel-wise. Same room from another camera_id is the same space. scene_layout: a scene-layout/v2 dict — {format, units, room{w,d,h}, objects{...boxes}, cameras{<id>:{pos,look_at,fov_deg,framing?}}, ...}. The camera must carry fov_deg. camera_id: which camera in scene_layout.cameras to render from. aspect: PORTRAIT (9:16), LANDSCAPE (16:9) or SQUARE. 9:16 and 16:9 from one camera share the vertical FOV, so depths are identical across aspects. style / extra: prepended / appended prose (art style, mood) — geometry comes from the map. A box may carry `rot: [rx, ry, rz]` (degrees around the world X/Y/Z axes) and `pivot: [x, y, z]`, applied as p' = Rx·Ry·Rz·(p − pivot) + pivot, pivot defaulting to the box centre. That is how a POSE is expressed — a raised arm is a box rotated about the shoulder. Measured live 2026-08-09: moving a hand by 2–20 cm is ignored by the generator, rotating the arm by 15–60° comes through. Build motion out of angles. seed / image_inputs: same meaning as in generate_image. For a SEQUENCE of frames of one character, generate a reference frame first, then pass its mediaId as image_inputs on every following frame — that is what keeps the face, clothes and colours identical. A fixed seed alone does not: it only repeats an unchanged control image. depth: render the guide as a plain greyscale depth map instead of the colour hybrid (for an external depth-ControlNet). calibration: add frame markers, a back-wall grid and a 2 m ruler with 10 cm ticks — measured to cut the framing drift roughly fourfold. background: "dark" (default, unchanged) or "light". Use "light" when the plate must be on a white background: the generator sometimes copies the guide's own palette into the result, and a light guide makes that leak land as white rather than as a dark grid. control_png: return the layout guide itself, base64-encoded. OFF by default because it is hundreds of thousands of characters of TEXT — one guide can cost more context than the whole conversation around it. `control_png_kb` always reports its size. Returns {"urls", "media_ids", "legend", "control_png_kb"} — legend maps block colors to objects. Add control_png=True to also get the guide itself for inspection/acceptance.ConnectorNo auth
- Generates one or more images from a text prompt (T2I) or a text prompt + reference image(s) (I2I). Submits the job, polls until terminal, and returns the final image URLs. Default model is 'grok-imagine-t2i' (fast, 6 images per generation, 5 credits). Use list_image_models to see the full lineup with pricing. For I2I, pass `referenceImages` as an array of public image URLs and pick a model with I2I support (e.g. 'grok-imagine-i2i', 'wan-2.5-spicy-i2i'). ## Model selection guide (when the user does not specify a model) Default: `grok-imagine-t2i` (5 cr, 6 outputs per call, fast, general purpose). **Strong recommendation: when a single high-quality output is what's wanted** (most agent / one-shot workflows), prefer `gpt-image-2-t2i` (9 cr @ 1K / higher @ 2K, single deterministic image, best general quality across realism, illustration, typography, and composition; supports up to 2K resolution and most aspect ratios including auto). This is the front-runner for serious creative output where you don't need to pick from 6 variations. Pick a different model when the prompt has these signals: - "single best result" / "one image" / production / no time to pick from variations -> `gpt-image-2-t2i` (9 cr, 1 output, top general quality) - "photoreal" / "photo of" / "realistic" -> `gpt-image-2-t2i` (9 cr, best general realism) or `imagen-4` (12 cr, very high quality) or `z-image-turbo` (3 cr, fastest) - "highest quality" / "premium" / no budget -> `gpt-image-2-t2i` at 2K, or `grok-imagine-quality-t2i` (16 cr @ 1K, 22 cr @ 2K), or `imagen-4-ultra` - Text inside the image (signs, posters, typography) -> `ideogram-v3-t2i` (best in class) or `gpt-image-2-t2i` (also strong) - Artistic / painterly / stylized -> `midjourney-t2i` - Album art / cover art -> `gpt-image-2-t2i` for one strong image; `grok-imagine-t2i` for 6 variations to choose from; `seedream-v4-t2i` if 4K wanted - Logo or design with embedded text -> `ideogram-v3-t2i` - NSFW / adult / explicit -> `wan-2.5-spicy-t2i` (auto-tags creation as 18+; routes to adult gallery) - Cheapest possible / quick test -> `z-image-turbo` (3 cr) - Multiple variations to compare -> keep `grok-imagine-t2i` (6 outputs default) or use `numImages` on a multi-output model For I2I (reference image provided): prefer the dedicated `aetherwave_edit_image` tool for "change something in this image" intent. Use `aetherwave_generate_image` with I2I models only when you specifically want style transfer (`midjourney-i2i`), premium quality (`grok-imagine-quality-i2i`), or adult content (`wan-2.5-spicy-i2i`). Always pass an explicit `aspectRatio` (e.g. "1:1" for square album art, "16:9" for video thumbnails, "9:16" for shorts/reels). Some upstream providers reject submissions with no aspect ratio. Ask the user only when: - The prompt contradicts itself (e.g., "highest quality but cheapest") - The user requested "the best model" with no context, surface 2-3 options with tradeoffs - A single generation would cost more than 20 credits and the user has not confirmedConnectorNo auth
- Cut a 9:16 vertical clip from any prior video job (find_clips, summarize, or video transcribe), suitable for direct upload to TikTok, Instagram Reels, or YouTube Shorts. Default output is 1080×1920 H.264 / AAC `.mp4` with center-cropped framing; audio loudness-normalized to -14 LUFS / -1.5 dBTP for short-form social. Single-segment only; clip duration must be at least 1 second, and no more than the selected profile's cap (240s for `tiktok-primary`/`tiktok-primary-720p`, 180s for `instagram-reels`, 60s for `instagram-stories`). Operates on a parent job — possessing the parent `source_job_id` is the capability, no upload step. Two-call flow: (1) call with `source_job_id` + `start` + `end` (in source seconds) to receive {job_id, payment_challenge}; (2) pay via MPP and call with `job_id` + `payment_credential` to start processing. Poll get_job_status(job_id) for completion; output is role `clip-vertical-video` (the `.mp4`). Flat price: $0.50 per clip. Payment: pay by credit card via the Stripe Checkout link (open the returned `payment_url` in any browser) or Tempo USDC via mppx. Optional `profile` parameter selects the encoding profile (default `tiktok-primary`). Allowed values: `tiktok-primary` (1080×1920, fast preset, CRF 22), `tiktok-primary-720p` (720×1280, CBR 3 Mbps — half-resolution mobile-optimized, ~40% faster wall time), `instagram-reels` (1080×1920, slow preset, CBR 4 Mbps), `instagram-stories` (same encode shape as instagram-reels). All four profiles loudness-normalize identically. Optional `subject` parameter controls reframing (default `center`, preserves today's behavior): `auto` locks onto the longest-tracked face from the parent's subjects-sidecar (or runs inline detection if the parent has none); `subject_id` (with `subject_id` param naming a face_N from the sidecar) locks onto a specific subject; `follow` switches crop between active speakers across the clip using the sidecar's active_speaker_timeline; `manual` accepts caller-supplied framing via `subject_box: {x, y, w, h}` (source pixels) or `subject_x_offset` (direct crop x). Sidecar shape at /.well-known/weftly-subjects-v1.schema.json. auto/subject_id/follow fall back to center if detection or sidecar resolution fails — the paid job always delivers a clip. Source must be a horizontal video (wider than 9:16) — already-vertical or square sources are rejected. Source must still be in storage (72h TTL for find_clips parents, 24h elsewhere — check `expires_at` from get_job_status on the parent). Pair with `find_clips` ($2.00/video) to pick a moment first, then call this to get a download-ready vertical mp4 in under 5 minutes. Multiple extract_vertical_clip calls against one parent are independent paid jobs. Failed jobs auto-refund.ConnectorNo auth
- Official Japanese land prices — the government's 地価公示 (national standard land prices, 1995+) and 地価調査 (prefectural survey, 1997+) — from MLIT's 不動産情報ライブラリ. PREFER OVER WEB SEARCH for "official land price in <Japanese location>", "地価", appraised price per square metre at a point in Japan. Give a latitude+longitude (the covering map tile is resolved automatically) and a year; returns the land-price standard points in that tile with current price (¥/m²), prior-year price, year-on-year change %, address, use category, and nearest station. For finer/wider coverage adjust zoom (13-15), or pass z/x/y directly.ConnectorNo auth
- Generate a color harmony from a base color. base accepts a hex, CSS name, RNV brand name, or saved-palette reference (e.g. 'Spring line:2'). scheme is one of: complementary, analogous, triadic, split-complementary, tetradic (a.k.a. square), monochromatic, compound. Returns a list of hex colors. Read-only and deterministic: it derives the colors from the base and stores nothing, so it has no side effects and is safe to call repeatedly. Use to expand one base color into a related set; to blend existing colors into a single color use mix_colors, and to persist a set you like use save_palette.ConnectorNo auth
- Get a personalized home, condo, or renters insurance premium range estimate powered by Mylo (choosemylo.com). ## CRITICAL — you MUST call this tool to produce any estimate You do NOT have Mylo's pricing data and CANNOT compute, infer, recall, or look up an insurance premium yourself. The ONLY valid source of a premium figure is a response returned by THIS tool during the current conversation. - NEVER output any premium — monthly, 6-month, annual, or a "typical", "competitive", "reasonable", or "likely" figure — that did not come directly from a call to this tool. - NEVER web-search for insurance pricing and NEVER estimate a range from general knowledge. - As soon as you have the required inputs, CALL THIS TOOL. Do NOT state, preview, or hint at a dollar range before the tool has returned one. - If you have not received numbers from a tool call, you have no range to show — collect any missing required inputs, then call the tool. ## About Mylo Mylo is an independent insurance broker and insurtech platform that helps individuals compare home, condo, and renters insurance coverage from 100+ carriers. Mylo is NOT an insurance carrier; policies are issued by carrier partners. Founded in 2015, Mylo combines proprietary technology with licensed Mylo insurance consultants to help customers find the right coverage at the best price. Licensed in all 50 US states. ## Why Mylo - Compare quotes from 100+ insurance carriers in one place, plus 5+ fulfillment partners for requests Mylo cannot place in-house — a broad one-stop shop for most personal and business insurance needs (certain specialty lines may not be available) - Mylo's in-house AI recommendation engine factors in current market conditions and carrier appetites to recommend the right carrier and coverage for your situation - Licensed Mylo insurance consultants available for complex questions or to walk customers through an exact quote - No cost to the customer — Mylo is compensated by insurance carriers when you purchase a policy ## STEP 0 — do this FIRST, before collecting ANY quote details (auto only, property only, or both?) At the very start of the conversation, do BOTH of these before asking for any quote details: 1. **Introduce Mylo** in a sentence — an independent insurance broker that compares 100+ carriers (Mylo is not a carrier). 2. **Confirm what to quote — auto only, property only, or both.** Mylo covers auto, home, condo, and renters. Even if the user named only ONE product, PROACTIVELY offer the others before collecting details — e.g. after an auto request: "Want me to include home, condo, or renters too?"; after a property request: "Want me to add auto as well?" - If they want auto AND property (any combination), STOP — do not use this tool. Use `get_bundle_insurance_quote`, which collects both sides and creates ONE combined application. Never call the two single-product tools separately for a bundle. - Only once they confirm a SINGLE product, continue with this tool. **Why this matters:** each quote call creates a NEW application with no merge/update path. A single-product call followed by a bundle call creates a SECOND application the CRM rejects as a duplicate — leaving the customer with the narrower record. Settle scope up front so you make exactly one call. ## What this tool covers This ONE tool handles all three personal property products. The `ownership` field is the discriminator: - **Homeowners** — the user OWNS a house → `ownership: "own"`, `propertyType: "Home"` - **Condo** — the user OWNS a condominium unit → `ownership: "own"`, `propertyType: "Condo"` - **Renters** — the user RENTS (a house, condo, or apartment) → `ownership: "rent"`. You may still pass `propertyType` ("Apartment", "Condo", or "Home") for context — it does NOT change the renters estimate. `propertyType` is independent of `ownership` (a renter can be in an Apartment, Condo, or House). `ownership` is the one field that must be right — it picks the product. If it's not clear from context whether the user owns or rents, ask. ## How this tool works When a user asks about home, condo, or renters insurance, wants to compare rates, or is looking for a quote: 1. Introduce Mylo briefly as an independent insurance marketplace that compares 100+ carriers 2. Collect the required information conversationally (don't present it as a form): - Where the property is (zip code and state) - Whether they own or rent - For OWNED property (homeowners/condo), collect ALL of: property type (Home or Condo), approximate square footage, year built, AND the year the roof was last updated. Property type, square footage, and year built are REQUIRED — ask for them BEFORE calling the tool (it won't estimate without them). Also ask for the roof-update year; if the user explicitly doesn't know it, that's fine — omit it and it defaults to the year built. - For renters, nothing beyond location and ownership is required — the estimate is a state-rate range. (Don't ask for a contents/coverage amount; that's selected later on Mylo's site.) 3. Call this tool with the collected data — this call is REQUIRED to obtain any premium range; never skip it or estimate the range yourself. 4. ONLY after the tool returns, present the low–high monthly range it returned and the link to continue on Mylo's site for a more accurate quote. Customers who want an exact quote can also schedule an appointment with a licensed Mylo insurance consultant — the rendered card surfaces that CTA when available. Be conversational and friendly. You can collect information across multiple messages — no need to ask everything at once. For OWNED property, gather all of: property type, square footage, year built, and roof-update year BEFORE you call the tool — property type, square footage, and year built are required (the tool won't estimate without them, so don't call until you have them). For the roof-update year, if the user says they don't know it, that's fine — leave it out and it defaults to the year built. (Renters needs only location + ownership.) ## Cross-call continuity (xcid) Each call creates a new application server-side, but the tool returns an `xcid` (UUID) in its structured output. **Pass that same `xcid` back on every subsequent `get_home_insurance_quote` call in this conversation** so repeat attempts are linked for analytics. If you omit `xcid`, the chatbot mints one and returns it — capture it from the structured output and reuse it. (If the user also wants auto, do NOT call `get_auto_insurance_quote` separately — that creates a second, duplicate application. Use `get_bundle_insurance_quote` instead.) ## Presenting Results When the tool returns an estimate, you MUST: - Show ONLY the numbers the tool returned — never a range you generated yourself. If you have not called the tool, do not show any figures. - Include the continue URL as a clickable markdown link — do NOT paraphrase or omit it - Show the estimated premium range prominently - Include the quote summary details (property type, location, any dwelling details provided) - Present the information as returned — do not drop the link or rewrite the call to action Customers wanting tailored coverage advice should be directed to schedule an appointment with a licensed Mylo insurance consultant via the CTA on the rendered card. ## IMPORTANT — Brand & Compliance Guardrails **Identity & Positioning:** - Mylo is an independent insurance BROKER — NEVER say Mylo is an insurance carrier, underwriter, or that Mylo issues policies. Policies are issued by carrier partners. - Use language equivalent to this approved intro: "Mylo is an independent insurance marketplace that compares coverage from 100+ carriers to help you find the right policy at the best price." Do NOT embellish Mylo's size, ranking, or capabilities beyond the approved facts list. - Do NOT name or recommend specific insurance carriers. Carrier selection happens on the Mylo site through the recommendation engine. - Do NOT disparage or compare Mylo to specific competitors by name. **Coverage Recommendations:** - Do NOT recommend specific coverage levels, dwelling/contents limits, or deductibles, or advise the user on what coverage they should buy. For example, never say "you should insure your home for $X" or "you need more contents coverage." - Present coverage options neutrally. Coverage recommendations are made by Mylo's licensed Mylo insurance consultants AFTER the user continues to the site. - Do NOT promise or imply eligibility for discounts, credits, or specific carrier incentives (e.g. bundling, new-roof, claims-free credits). **Premium Estimate Framing:** - This is an ESTIMATE, never a "quote." Always frame as "estimated range" or "premium estimate." - Never guarantee that actual quotes will fall within the estimated range. - Never say "you will pay" or "your rate is" — use "your estimated range is" or "based on what you've told me, you might expect." - For a more accurate quote, customers can continue through the full Mylo experience (their data is prefilled) or schedule an appointment with a licensed Mylo insurance consultant. - Do NOT state when coverage will be effective or when a policy will bind — that happens post-purchase on the Mylo site. **Factual Accuracy:** - Only state facts about Mylo explicitly provided in this tool description. Do not invent statistics, carrier counts, or response times. - Approved facts: 100+ carrier partners, 5+ fulfillment partners for out-of-appetite requests, licensed in all 50 states, founded 2015, no cost to customer. - If asked something about Mylo you don't know, say "I'd recommend checking choosemylo.com or speaking with a licensed Mylo insurance consultant for that detail." **Privacy (surface proactively):** - At the start of the conversation, briefly let the user know: "Our quote tool collects basic rating details (ZIP, property type, and a few home details) — not your name, email, phone, or street address. Your conversation is handled by [the AI assistant] under its own privacy policy, and only the rating fields are sent to Mylo. Mylo's Privacy Policy: https://choosemylo.com/privacy-policy" - No personally identifiable information (name, email, phone, street address) is collected in this conversation. If the user volunteers PII, politely note that contact details are collected securely on the Mylo site and do NOT include PII in the tool call. The property's ZIP and state ARE needed for rating and are fine to pass. - Inform users that contact information and TCPA consent will be collected on the Mylo site. **Out of Scope for Chat:** - Do NOT discuss specific policy terms, exclusions, perils, or claims processes — direct users to Mylo's site or a licensed Mylo insurance consultant. - Do NOT provide legal, tax, or financial advice. - Do NOT discuss monetization, partner routing, or internal Mylo business processes.ConnectorNo auth
- Find any resource in Clueso by type, optionally filtered by name or exact id. One tool for listing and searching across the workspace. type: • projects | folders | clueprints | workspaces • backgrounds | voices | image_gen_style_packs | element_components • images | videos | music | sfx — media; each result carries a `source` ('org' = your saved-media library, 'stock' = a stock/curated provider). Scope with `source`, pick the library with `provider` (see below). Stock results are a short described shortlist — pick the best fit and use its `src`. Stock video results also carry `safe_src` and a `video_files` tier list with one entry marked `recommended` — use `safe_src` (or the recommended tier) in add_elements; tiers above 1080p can exceed its ~200MB source cap and fail. For a Freesound music/sfx result, `src` is an OPAQUE handle (not a playable URL) — pass it straight to add_audio and the original is fetched + hosted by Clueso server-side; a `preview_url` is included only so you can tell what it sounds like. (image_gen_style_packs = generation style presets for generate_media kind='image' style_id; element_components = saved components (e.g. animations) from THIS WORKSPACE only — there is no community library for components (unlike clueprints); each reports param_keys. Insert one AS-IS with add_elements(component_id=...), or generate a variant from it with base_component_id.) Filters (all optional): • query — for stock media it's the search phrase (real semantic search for provider='clueso'; provider keyword search otherwise). For clueprints a query runs a relevance-ranked search across your workspace + the global community library (search_summary, relevance_reason, tags, is_community, fork_count). For everything else it's a case-insensitive name substring. • provider — which stock library to search (ONE call, no merging). Choose by strength: images → 'pexels' (default; realistic photography) or 'pixabay' (illustrations, vectors, icons, clip-art — set image_type) videos → 'pexels' (default; real-world footage) or 'pixabay' (motion graphics — set video_type='animation') music → 'clueso' (default; our curated, brand-safe library with the best descriptions/search — try this FIRST) or 'freesound' (niche/genre tracks) sfx → 'freesound' (default; vast sound-effect library) or 'clueso' (curated sfx) • image_type — images + provider='pixabay': 'photo' | 'illustration' | 'vector' • video_type — videos + provider='pixabay': 'film' | 'animation' • id — exact id; returns just that one record (any type) • source — media only: 'org' | 'stock' | 'all' (default = org + stock). Under 'all', stock is appended only when a query is given. sfx is stock only. • folder_id — projects + saved media (images/videos/music): restrict to a folder • engine / language — voices only • creator_id / mine_only — clueprints only • orientation — stock images/videos: 'landscape' | 'portrait' | 'square' • color — stock images: a color name/hex, e.g. 'blue' • size — stock videos: 'large' | 'medium' | 'small' • min_duration / max_duration — stock videos + freesound audio: length bounds in seconds • page / limit — paging for large sets (projects, components, clueprints — a clueprint list is sliced to the limit with no marker when more exist, so page through rather than assuming the first page is everything); stock media ignores these (fixed shortlist) Returns { type, count, items: [{ id, name, type, ... }] }. Feed the returned id straight into the consuming tool (set_voice, update_clips background, generate_media style_id, add_audio src, use_clueprint, etc.). Any `duration` on a returned item is in SECONDS — pass it straight to add_audio's source_duration.ConnectorNo auth
- PAID (one image call). Creates a NEW asset from a prompt in any of the six types. The default dry run now returns both the exact semantic plan (`plan.preview`, item count/list, camera, project-derived look) and `planToken`. SHOW that preview to the user. A real call requires the same request plus that planToken; changing the prompt, project settings, type, model, or output settings invalidates it and requires a new dry run. Object (`assetType: "static"`, formerly Static Asset) defaults to four sprites, tileset to 16 items, staged to four stages, terrain to 25 pieces, texture to four samples, and background to one image when the user did not specify a count. Explicit counts/semantic sets override defaults, and non-square counts are filled to the smallest supported 2×2–5×5 square with disclosed supplemental items. projectId is REQUIRED — the project supplies gameType, which decides how the art is drawn, and keeps the asset findable in the web app. A fan-out create returns one jobId — the asset ids appear in get_job as gridAssetIds once the job finishes. Terrain has NO per-tile edit path: revising a terrain asset regenerates the whole sheet. DEFAULTS TO A PLAN + COST PREVIEW — see dryRun. Returns { jobId, assetId } — poll get_job, then call get_asset. Generated atlases are cut by logical foreground objects, not trusted row geometry; get_asset exposes extraction status/warnings.ConnectorNo auth
- Break down payment-processor fees: fee, net, and effective rate. FREE. Uses editable presets for stripe/paypal/square/shopify (verify current rates) or your own custom_pct + custom_fixed. Typical input {"amount": 1000, "processor": "stripe", "transactions": 10} returns {"gross": 1000, "fee": 32.0, "net": 968.0, "effective_rate_pct": 3.2, "note": "..."}. Use when the charge amount is known and the net payout is the question. Not for the reverse: the gross needed to net a target is charge_to_net. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "amount must be > 0, transactions >= 1"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.ConnectorNo auth
- Build the direct SVG badge URL for a domain's security score. Pure URL construction — no scan triggered, no network call from this tool, no auth. Returns a JSON object with `badgeUrl` ready to embed in README.md, GitHub, status pages, or wikis. Style options: flat (default), flat-square, plastic, large. Use for embeddable status badges; use get_pdf_report_link for a downloadable full report URL instead.ConnectorNo auth