Skip to main content
Glama
760,002 tools. Updated 2026-11-09 10:17

"Transmission" matching MCP tools:

  • Query verified U.S. generator-level operating, planned, retired, or canceled power capacity from EIA-860M. Use this for capacity questions by state/jurisdiction, county FIPS, source-reported balancing authority code, fuel, prime mover, technology, lifecycle, or year. Pass filters inside the `params` object. The operating/planned/retired/canceled selector is `lifecycle` (e.g. `lifecycle: "operating"`, the default) — there is no `status` or `status_group` parameter. Returns JSON aggregates with citations and optional generator-level records when `include_records` is true. Does not determine electricity supplied, generation MWh, real-time dispatch, capacity factor, battery storage throughput/duration, demand/load, prices, data-center load, or transmission deliverability. For capacity REQUESTED in an ISO interconnection queue (projects pending interconnection, not yet built), use the relevant ISO's queue tool: query_power_interconnection_queue_v1 (MISO), query_power_interconnection_queue_pjm_v1 (PJM — or query_power_interconnection_queue_pjm_cycle_v1 for PJM's cluster/cycle grid), or query_power_interconnection_queue_caiso_v1 (CAISO).
    ConnectorNo auth
  • Query PJM's cluster/cycle service-request grid — the cluster view of PJM's interconnection process: the TC1/TC2 transition cycles (re-processing the pre-Order-2023 serial backlog) and the reopened steady-state cycles (C01+, the new intake). A SEPARATE PJM publication from the full New Services queue (query_power_interconnection_queue_pjm_v1) — richer per-project cluster detail; the two share rows and are never combined. Returns cited, project-level records with PJM's full cluster schema: the cluster `cycle` (TC1 / TC2 / C01 …) and `stage` (phase / decision point), the `developer`, requested megawatts (`requested_max_output_mw` = MFO, `requested_summer_mw`, `requested_winter_mw`), the realized built `in_service_mw`, long-term-firm transmission `ltf_mw`, location (`state`, `county`, derived `county_fips`), `fuel` and `project_type` as PJM reports them, the single `status`, and the phased System-Impact-Study report URLs + statuses. Group or filter by `cycle`, `stage`, `status`, `state`, `county_fips`, `project_type`, `capacity_or_energy`, `fuel`, `developer`, `transmission_owner`, or (group only) `is_hybrid`; filter `submitted_date` by range. Pass each parameter as a top-level key of `params` (flat). Example: `{"cycle": "C01", "status": "Active"}` for the live reopened-cycle pipeline; `{"group_by": ["cycle"]}` for counts by cluster cycle. Returns JSON aggregates with citations and optional row-level records when `include_records` is true; every value carries `source`, `as_of`, and a `source_row` verifiable with get_source_evidence_v1. The `requested_*` figures are REQUESTED capacity, not built: historically the large majority of queued megawatts withdraw before they are built. NEVER read a requested-MW total as installed/operating capacity — additive across distinct projects but a REQUESTED total only. PJM also reports `in_service_mw` (the realized built MW). For built/operating capacity use query_power_capacity_v1. PJM cluster grid only. This and PJM's New Services queue (query_power_interconnection_queue_pjm_v1) are different publications that share rows — never summed or compared across them; never across ISOs (the MISO queue is query_power_interconnection_queue_v1; the CAISO queue is query_power_interconnection_queue_caiso_v1; the NYISO queue is query_power_interconnection_queue_nyiso_v1; the ISO-NE queue is query_power_interconnection_queue_isone_v1; the ERCOT queue is query_power_interconnection_queue_ercot_v1; the SPP queue is query_power_interconnection_queue_spp_v1). PJM reports no data-center / load type, and this tool does not infer one.
    ConnectorNo auth
  • Query the ISO-NE generator interconnection queue — ISO New England's public IRTT "public queue" report, the waiting line of projects that have REQUESTED to connect to the New England grid (CT, MA, ME, NH, RI, VT). Returns cited, project-level records with ISO-NE's full published structure (all 31 columns of the rendered report): the three megawatt readings kept SEPARATE (`net_mw`, `summer_mw` = max summer output, `winter_mw` = max winter output — `net_mw` is 0 for the many Capacity-Network-Resource-only requests, a real value, not missing), the request `request_type` (G = Generation / ETU = Elective Transmission Upgrade / TS = Transmission Service), the space-delimited multi-value `fuel_type` (EIA energy-source codes, e.g. "SUN BAT"), the `unit_type` and service code `serv` (CNR = Capacity Network Resource / NR = Network Resource), the `jurisdiction` (F = FERC / N = Non-FERC), the ISO-NE load `zone`, the per-stage study statuses (`fs_status` … `ia_status`) with their study-document links, location (`state`, `county`, derived `county_fips`, `poi`), and lifecycle dates. Group or filter by `application_status`, `project_status`, `request_type`, `unit_type`, `fuel_type`, `serv`, `jurisdiction`, `zone`, `state`, `county_fips`, or `cluster`; filter `requested_date` by the `requested_date_from` / `requested_date_to` range. Pass each parameter as a top-level key of `params` (flat — not nested). Example: `{"application_status": "A", "request_type": "G", "state": "MA"}` for active generation requests in Massachusetts; `{"group_by": ["application_status"]}` for requested MW and project counts by status. Returns JSON aggregates with citations and optional row-level records when `include_records` is true; every value carries `source`, `as_of`, and a `source_row` verifiable with get_source_evidence_v1. `net_mw` / `summer_mw` / `winter_mw` are REQUESTED capacity, not built: historically the large majority of queued megawatts withdraw before they are built, so the queue is withdrawn-dominated. NEVER read a queue-MW total as installed or operating capacity — it is additive across distinct rows but is a REQUESTED total only. ISO-NE publishes net, summer-peak and winter-peak MW separately — served under ISO-NE's own labels and never blended into one nameplate. Scope by `application_status`: `A` = Active (the live pipeline), `C` = Commercial (built and in service — the built reading), `W` = Withdrawn. ISO-NE ALSO carries a separate build-progress `project_status` (Under Study / Under Construction / In Service / …) — kept distinct from `application_status`, never collapsed. For built/operating capacity use query_power_capacity_v1. ISO-NE only — never summed, deduped, or compared across ISOs. For the MISO interconnection queue use query_power_interconnection_queue_v1; for PJM use query_power_interconnection_queue_pjm_v1 (or query_power_interconnection_queue_pjm_cycle_v1 for PJM's cluster/cycle grid); for the CAISO (California) queue use query_power_interconnection_queue_caiso_v1; for the NYISO (New York, incl. load interconnection requests) queue use query_power_interconnection_queue_nyiso_v1; for the ERCOT (Texas) queue use query_power_interconnection_queue_ercot_v1; for the SPP (central US) queue use query_power_interconnection_queue_spp_v1. ISO-NE publishes no data-center / load request type (all rows are generation or transmission), and this tool does not infer one — that interpretation is the analyst's, from cited rows.
    ConnectorNo auth
  • Query the SPP generator interconnection queue — Southwest Power Pool's public GI Summary report, the waiting line of generation projects that have REQUESTED to connect to the SPP grid (the ~14-state central-US RTO: OK, KS, TX panhandle, NE, NM, MO, CO, ND, SD, AR, LA and more). Returns cited, project-level records with SPP's full published structure: the requested `capacity_mw` (SPP's headline `Capacity` figure) PLUS five other labeled MW columns SPP publishes — `max_summer_mw`, `max_winter_mw`, `requested_max_injection_mw`, `requested_nrd_mw`, `nameplate_capacity_mw` — served separately and NEVER blended; the `generation_type` (Wind / Solar / Battery/Storage / Thermal / Hybrid / Hydro — SPP encodes hybrids natively as `Hybrid`, so no is-hybrid is invented) and free-text `fuel_type` (slash-delimited combos like `Solar/Storage` kept whole); the study `current_cluster` (e.g. `DISIS-2024-001`, `Surplus`, `RTOE Transitional Cluster`) and regional `cluster_group` (`01 NORTH` … `05 SOUTHWEST`); the transmission owner `to_at_poi`; the `service_type` (`ER/NR`, `ER`, `NR`); the `substation_or_line`; and the lifecycle dates (`request_received`, `in_service_date`, `commercial_operation_date`, `date_withdrawn`). Group or filter by `native_status`, `generation_type`, `fuel_type`, `service_type`, `current_cluster`, `cluster_group`, `to_at_poi`, `county_fips`, or `state`; filter `request_received` / `commercial_operation_date` by their `_from` / `_to` ranges. Pass each parameter as a top-level key of `params` (flat — not nested). Example: `{"native_status": "DISIS STAGE", "generation_type": "Solar"}` for solar in the DISIS study stage; `{"native_status": "DISIS STAGE", "group_by": ["state"], "order_by": "capacity_mw", "top_n": 5}` for the active study pipeline's biggest states by requested MW. Returns JSON aggregates with citations and optional row-level records when `include_records` is true; every value carries `source`, `as_of`, and a `source_row` verifiable with get_source_evidence_v1. `capacity_mw` is REQUESTED capacity, not built: historically the large majority of queued megawatts withdraw before they are built — in the SPP file ~66% of rows are `WITHDRAWN`. NEVER read a queue-MW total as installed or operating capacity — it is additive across distinct rows but is a REQUESTED total only. Always scope by `native_status`, which is SPP's OWN status vocabulary served VERBATIM (`IA FULLY EXECUTED/ON SCHEDULE`, `IA FULLY EXECUTED/COMMERCIAL OPERATION`, `IA FULLY EXECUTED/ON SUSPENSION`, `IA PENDING`, `DISIS STAGE`, `FACILITY STUDY STAGE`, `SPECIAL STUDY`, `ERAS`, `TERMINATED`, `WITHDRAWN`, …); it is never mapped to a lifecycle enum and there is no derived active/withdrawn flag — that equivalence is the analyst's. For built/operating capacity use query_power_capacity_v1. SPP's GI Summary is regenerated on demand and SPP keeps no per-vintage archive, so this serves SPP's CURRENT queue (the response `as_of` is SPP's own "Last Updated On" stamp); it is NOT a deep point-in-time history — history accrues forward from first capture, so there is no `as_of` time-travel parameter. SPP only — never summed, deduped, or compared across ISOs. For the MISO interconnection queue use query_power_interconnection_queue_v1; for PJM use query_power_interconnection_queue_pjm_v1 (or query_power_interconnection_queue_pjm_cycle_v1 for PJM's cluster/cycle grid); for the CAISO (California) queue use query_power_interconnection_queue_caiso_v1; for the NYISO (New York) queue use query_power_interconnection_queue_nyiso_v1; for the ISO-NE (New England) queue use query_power_interconnection_queue_isone_v1; for the ERCOT (Texas) queue use query_power_interconnection_queue_ercot_v1. SPP's GI queue is GENERATION-only and infers no load/data-center type — that interpretation is the analyst's, from cited rows.
    ConnectorNo auth
  • Valide une demande de devis créée par `demander_devis`, à l’aide du code à 4 chiffres envoyé par SMS au demandeur. C’est cette validation, et elle seule, qui autorise la transmission de la demande aux installateurs certifiés RGE. Demande le code à l’utilisateur (il l’a reçu sur son mobile, valable 30 minutes) et appelle cet outil avec le `demande_id` renvoyé par `demander_devis`. Si le code est expiré ou après 5 essais infructueux, rappelle `demander_devis` avec exactement les mêmes coordonnées : un nouveau code sera envoyé, sans créer de doublon.
    ConnectorNo auth
  • Which prefectural weather forecasts did JMA issue for an area between two times? Lists each archived issuance (JMA issue time, transmission time, our fetch time, scheduled/unscheduled/correction/cancellation, bulletin URL and SHA-256) with coverage gaps where JMA's feed could not be read. Free window: last 30 days (an earlier since is clamped; see history_window). Use forecast_as_issued for the content. An archive, not a forecast service.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Use this first when a user wants to send or price a fax. PromptFax is built for irregular, pay-per-use outbound faxing: every real send requires a user-reviewed quote and Stripe payment authorization before transmission. MCP clients should set hostType to identify their host: chatgpt, claude, browser, or other. In ChatGPT, pass official files[] file parameters first when they are available so PromptFax can immediately import files[].download_url; never pass a raw file_id or local path as the document. The ChatGPT widget opens for destination entry, automatic quote creation, Stripe Checkout, status tracking, and Choose PDF from ChatGPT fallback when automatic attachment is unavailable or fails. If no document is attached, tell the user to attach a document in the widget. The widget does not provide a document preview step. Do not tell ChatGPT users to get a quote; after the widget has a document and valid destination, tell them to verify the price and use Pay & send when ready. Standards-compatible MCP Apps hosts use the inline PromptFax picker, and text-only clients use the hosted PromptFax session page or attach_document with a fetchable HTTPS URL. Do not call get_quote, checkout, or send_fax for a ChatGPT widget session unless the user explicitly asks for fallback behavior or the widget is unavailable. Use get_status only for a textual status refresh.
    ConnectorNo auth
  • Fetch the full advisory record for an OSV vulnerability ID. Returns the complete record: summary, full details text, CVE aliases, all affected packages and version ranges, fix versions, CVSS severity vectors, CWE weakness IDs, and references. Use when osv_query_package or osv_query_batch returns a vuln ID and you need the full advisory context — affected packages or remediation guidance. For overflow, repeat the original input with page: overflow.page. Continue the same path with offset: page.nextOffset and revision: page.revision until nextOffset is null. Retrieve each entries[].deferred.path separately at offset zero without a revision. Do not pass the output page object as input. Every page is a fresh lookup; restart a changed node without a revision. Transmission overflow and upstream truncation are separate; neither confirms clean.
    ConnectorNo auth
  • Calculates LoRa packet time-on-air using the Semtech AN1200.13 formula. Computes symbol duration, preamble time, payload symbol count, effective data rate, and the minimum transmission interval for 1% duty cycle compliance. Essential for capacity planning in LoRaWAN and Meshtastic mesh networks. Accepts spreading factor (SF7-SF12), bandwidth (125/250/500 kHz), coding rate (4/5-4/8), payload size, header mode, CRC, and optional low data rate optimization. Feeds airtime_ms to channel_utilization for mesh load analysis.
    ConnectorNo auth
  • Summarize the available money-market, FX, macro-capital and China evidence when a question spans markets or its scope is not yet clear. Start with section='summary', then select a relevant section. For detailed funding metrics use money_market_context; for dated FX/accepted China observations use market_workbench; for external dataset discovery use research_network. This chartless overview is not a time-series query. It projects only completed/public state into money_markets, forex, macro-capital transmission, China macro evidence, official references, methodology, or a compact summary. Every response carries snapshot/as-of clocks, canonical Seiche citation URLs, and explicit observed, derived, structural, restricted, and unavailable boundaries. The China structural catalog is unsigned; only status=restricted represents a verified Seiche owner-attested revision; both states keep NBS values, raw evidence, and history withheld. A separately operator-accepted economic_context may publish licensed World Bank WDI values with annual/structural freshness, distinct release, Palimpsest collection, and Seiche acceptance clocks. Those values are context only and never a live print, score, gauge, forecast, or signal. The sources selector is reference-only; use all when verified China context and its NBS source linkage must appear together. Coverage is curated and partial rather than exhaustive or uniformly live. It never triggers collection, repository history reads, or model fitting. Its named-field whitelist omits chart and history arrays for data minimization; that is not a per-record licensing audit. Capital coverage is limited to public positioning proxies, Treasury primary-market absorption, market stress, official liquidity and global dollar credit—not a security master, issuer-data service or consolidated tape. Executable depth, liquidity-provider concentration, and position-sized exit costs are outside this tool's scope.
    ConnectorNo auth
  • Search RENTAL CARS on HotelsCasa by city, country or geographic radius, with pickup/return dates, seats, transmission, class and price. Cars are a SEPARATE inventory from properties — use this tool only when the traveller asks about a car, never to answer an accommodation question. CARS ON HOTELSCASA: cars from local rental companies (offered_by:"rental_company") and from private owners. Cars marked instant:true are confirmed immediately; the rest are confirmed after booking by the rental company or by the owner, who replies personally. A rental-company car with similar_model:true guarantees the class, not the exact model. PRICE: price_day is the daily rate and total_eur the rental for the whole period. A car with price_day:null has NOT published a rate — that is normal and common, never call it unavailable or say the data is missing. Present it with its price_note and send the traveller to the booking_link to ask. GOLDEN LINK RULE: every car you present MUST include its booking_link verbatim, as a clickable link — never omit it, shorten it or strip its parameters. It is the only way the traveller can proceed. NEVER invent or reveal a phone number, an address or a licence plate: they are not in the data and are only shared through the booking flow. Coordinates are approximate on purpose (~200 m) — use them for "3 km from the centre", never as a pickup address.
    ConnectorNo auth
  • Use this when someone wants to buy a used car in Japan, or asks for a used car that fits a budget, a model year, mileage or a manual transmission. To narrow to a specific car, first find its generation with search_vehicles and pass model_id (or series_id for any generation of a series). Returns the cars that dealers list on car-gene.com and that are on sale now: {filters, sort, total, used_cars, next_offset}. Each car has model (the generation it is, with chassis_code and its page url), grade, minor_change_name, total_price_yen (the total payment to drive it away, including the dealer's fees; quote this price, never price_yen alone), price_yen (the body price), first_registration_year and month, mileage_km, inspection_year and month (the vehicle inspection is valid until then), repair_history (true when the car has had frame damage repaired), transmission, shop (the dealer's name, prefecture and city) and the url of its page on car-gene.com, where the photos, details and the inquiry form are. Both prices null means the price is on request. Budget filters use total_price_yen, so cars with the price on request are left out of them. The order is sort only. Cars are cut to fit the response size; when next_offset is not null, call again with offset set to it. Empty used_cars means nothing matched among the cars listed on car-gene.com, not that no such car is for sale elsewhere.
    ConnectorNo auth
  • BEHAVIOR: Outbound messaging operation. Routes proactive notifications to the human trader's verified Telegram chat, channel, or Discord webhook. Dispatches discretionary trade ideas, market condition updates, or risk reports to keep the user informed without waiting for prompts. PRICING: $0.001 USD per dispatch. Deducted from daily tariff quota or USD balance. PARAMETER INTERACTIONS: - 'target': Destination identifier string obtained from `user_account.list_destinations`. Prefixes determine transport: 'tg_user:' / 'tg_channel:' for Telegram, 'out_wh:' for Discord webhooks. Must belong to the authenticated account. - 'message': Main message body. For Telegram, supports HTML tags. For Discord, maps to the embed description. - 'title': Optional subject line. For Discord, renders as the embed headline. For Telegram, prepends as a bold header if provided. RETURNS: Structured JSON confirming transmission: 'status' ('dispatched'), 'target', 'message_length', 'timestamp_utc', and '_usage' (cost_usd and remaining quota/balance). USAGE GUIDELINES: Call `user_account` with action='list_destinations' prior to sending to retrieve valid target strings. Use this tool exclusively for informative messaging and human-in-the-loop updates. Do NOT use this tool to monitor market prices or set execution triggers (use `alert_manager` instead). ERRORS: Unauthenticated calls, unverified/foreign destinations, empty messages, or exhausted quotas return an explicit 'isError: true' payload.
    ConnectorNo auth
  • Annual electricity consumption of French sites (open data, no key). TWO GRID TIERS, and they are not interchangeable. `reseau="distribution"` (default) reads Enedis: consumption per ADDRESS, with the NAF division. `reseau="transport"` reads ODRE (RTE): the sites connected to the transmission grid, which are ABSENT from Enedis entirely — and they are the largest consumers in the country. Saint-Jean-de-Maurienne (73248) returns zero NAF-24 address on Enedis and 1,702,616 MWh on ODRE for 2023 — one IRIS (732480104) holding 3 delivery points, so that row comes back marked `maille="iris_agrege"`, not as a single site. A "heavy electricity user" list built on distribution alone is a list without the heavy users: use `reseau="les_deux"` for a real one. ⚠️ THE TRANSPORT TIER IS A YEAR BEHIND. ODRE's newest millésime is older than Enedis's (2023 against 2024, measured 2026-09-09). Asking ODRE for a year it does not carry returns ZERO rows for the whole tier — which reads exactly like "no transmission-connected site here" while it means "that year does not exist yet". That zero is now NAMED in `avertissement_millesime`: read it before concluding. Nothing is invented to fill the hole — an absent year stays absent, it is only said out loud. TWO GRAINS, and `maille` governs BOTH tiers with the same meaning: "site" = one row is one site. On DISTRIBUTION, Enedis publishes ONE ROW PER ADDRESS AND PER NAF DIVISION, so `maille="ligne"` (default) returns rows, and thresholding them one by one MISSES sites whose divisions are each below the bar but whose total is above it; `maille="site"` sums an address's divisions and applies `min_mwh` AFTER the sum — the grain almost every caller means. A site then carries `naf2_principal`, `naf2_detail` and `multi_naf2`. On TRANSPORT, "site" keeps only the IRIS that hold a single delivery point, and "ligne" also returns the aggregated ones. Filtering those out is how a query for the largest consumers returns the small ones — see `maille` below. Rows Enedis publishes without an address are real consumption that cannot be located: they are never returned as sites, and counted in `lignes_ignorees` / `mwh_ignores` instead of being silently dropped.
    ConnectorOAuth
  • Scheda tecnica di QUALSIASI modello del mercato italiano dal catalogo Motornet, anche se NON in vendita o a noleggio sul network DealerMAX. È il tool "enciclopedico": caratteristiche di un'auto a prescindere dalla disponibilità reale. QUANDO usarlo: domande tecniche slegate dall'inventario (dimensioni, consumi, potenza, autonomia BEV, 0-100, posti, neopatentati) e confronto allestimenti dello stesso modello. QUANDO NON usarlo: per auto USATE realmente in vendita/noleggio → search_vehicles o search_nlt_offers; per il dettaglio di UN annuncio (prezzo live, foto, dealer) → get_vehicle_details o get_nlt_offer_details; per le FAQ del mercato → get_market_intel. NON conosce prezzi, disponibilità né dealer: solo catalogo tecnico. Ritorna {query, filters, total, items[], rate_limit}. Ogni voce di items[] è UN allestimento (una query può restituirne più dello stesso modello): brand, model, trim, body, fuel_type, engine, performance, dimensions_mm, weight_kg, boot_capacity, tyres, transmission, drivetrain, emissions_co2_g_km, consumption_l_100km, country_of_production, novice_drivers_allowed, ev (autonomia + ricarica per BEV), pneumatic_suspensions, short_description. Read-only, keyless. Rate limit 60 richieste/min per IP.
    ConnectorNo auth
  • Fallback/non-widget tool for creating a user-reviewable pay-per-use fax quote when you have a fax number and either an MCP session, a PromptFax documentId, or one or more HTTPS PDF URLs. A quote is required before Stripe Checkout and before any real fax transmission. In ChatGPT widget sessions, do not call this after start_session because the widget auto-quotes once the document and destination are ready.
    ConnectorNo auth
  • Query vulnerabilities for multiple packages in one call — the primary tool for dependency audits, SBOM scanning, and lockfile triage. Pass up to 1000 mixed {name, ecosystem, version} tuples and {purl, version?} identifiers, with exactly one embedded or separate version per PURL. Each entry in the response corresponds positionally to the input. Each finding includes CVE aliases for chaining to nist-nvd-mcp-server for CVSS scoring. Large replies retain the complete summary. For overflow, repeat the original packages array with page: overflow.page. Continue the same path with offset: page.nextOffset and revision: page.revision until nextOffset is null. Retrieve each entries[].deferred.path separately at offset zero without a revision. Do not pass the output page object as input. /results/17 selects original input row 17, even when earlier rows failed. Pages are fresh lookups and do not recompute the initial summary; restart a changed node without a revision. Transmission overflow and upstream truncated are separate; neither confirms clean.
    ConnectorNo auth
  • Search Tuki rental cars (also covers transfers/traslados, which on Tuki are handled as rental vehicles). Filter by free text or transmission. Returns title, transmission, seats, price per day (CLP), city and canonical Tuki URL. Use for "arrendar auto en San Pedro", "rent a car Atacama", "traslado/transfer". NOTE: for ski/snowboard GEAR rental (arriendo de esquis / equipo de nieve, e.g. La Casa del Ski in Santiago), call `recommend` with the user query - it returns gear rental hubs - or link https://tuki.cl/nieve.
    ConnectorNo auth
  • Analyze a proposed AI-agent tool call before execution and return a deterministic, policy-aware decision (allow, notice, confirm or block) covering destructive actions, sensitive-data exposure, external transmission, privilege changes and irreversible operations, under the applicable policy — permissive, balanced or strict, balanced by default. Filesystem paths outside a known workspace_root are treated as higher risk than paths inside it.
    ConnectorNo auth
  • Analyze a proposed AI-agent tool call before execution and return a deterministic, policy-aware decision (allow, notice, confirm or block) covering destructive actions, sensitive-data exposure, external transmission, privilege changes and irreversible operations, under the applicable policy — permissive, balanced or strict, balanced by default. Filesystem paths outside a known workspace_root are treated as higher risk than paths inside it.
    ConnectorNo auth
  • Use this for "when will this show up on my credit report" or "what day does my bank report". Returns how the monthly reporting cadence works in Canada, how long a change takes to appear on a file, and why an Equifax file and a TransUnion file for the same person differ. This bundled reference has no verified per-issuer transmission calendar and returns no exact reporting day. Returns bundled reference material, optionally filtered or calculated from inputs; does not fetch live data or change accounts.
    ConnectorNo auth