"Foundry Virtual Tabletop" matching MCP tools:

• calculate_chip_costA

  Silicon AnalystsA

  Pure-function chip cost estimator. Given die dimensions (mm), process node, and optional packaging/HBM parameters, returns: estimatedChipCost (USD), dieArea (mm²), grossDiesPerWafer, frontendYield (%), totalYield (%), and a costBreakdown {waferCostPerGoodDie, packagingAndTestCost, hbmCost, marginCost}. USE THIS for: hypothetical chip cost modeling, sensitivity analysis, fabless tapeout decisions. DO NOT USE for: published cost of an existing accelerator (use get_accelerator_costs); wafer pricing only (use get_wafer_pricing). Required: dieWidth, dieHeight (1–33 mm reticle limit). Errors with INVALID_PARAMS if outside bounds. processNode defaults to tsmc-n5; valid nodes via get_wafer_pricing. Estimates are directional ±15–20%. Optional energy adder: pass energyRegion (texas|ohio|arizona|china|korea|taiwan|germany) to get a conditional `energy` block — regional manufacturing-electricity cost per die (SA estimate; wafer price already embeds foundry energy, so treat it as a scenario delta). energyFacilityOverhead=false drops the ~1.75× facility multiplier. Optional substrate scenario: pass substrate=panel-310x310 to model CoPoS panel-level assembly — applies the midpoint of Yole's realistic 20–30% panel cost-savings band to the packaging cost ONLY (silicon GDPW unchanged; panels are back-end). Conditional `substrateScenario` block + SA-scenario meta note. TSMC CoPoS: pilot ~June 2026, mass production 2028–29 — a forward-looking scenario, not a quote.

  ConnectorNo auth

• estimate_lead_timeA

  Silicon AnalystsA

  Heuristic chip manufacturing LEAD TIME estimator (MANUFACTURING CYCLE TIME). Given total mask layers (or a processNode to default them), foundry utilization % (optional — defaults from live foundry-allocation data), and packagingType, returns min/max bands: fabDays, fabWeeks, packagingWeeks, totalWeeks, plus effectiveDpml (days per mask layer), the operating-curve weight, a resolved-inputs echo, assumptions, methodology, and public-source citations. USE THIS for: "how long to manufacture this chip" — wafer-fab cycle time + packaging assembly/test time for hypothetical chips; cycle-time sensitivity to fab utilization or packaging class (conventional vs flip-chip vs CoWoS). DO NOT USE for: booking windows / allocation lead time — how long until a booked-out foundry STARTS wafers, publicly 52–156+ weeks at N3-class nodes and CoWoS (use get_foundry_allocation); chip cost (use calculate_chip_cost / get_accelerator_costs). Provide maskLayers (integer 10–200) or processNode (tsmc-n3 | tsmc-n5 | tsmc-n7 | tsmc-n16 | tsmc-28 | samsung-3nm | samsung-5nm | samsung-7nm | samsung-14nm | intel-7 | intel-16 | gf-12lp | gf-fdx | umc-22-28 | umc-40 | smic-28). packagingType accepts coarse classes (conventional | flip-chip | cowos, default flip-chip) or any platform packaging id (fc-bga, wirebond-bga, cowos-l, copos, ...). Utilization ≤80% settles at the best-case band; ≥95% converges to the worst-case bound (FabTime operating-curve shape). Heuristic from public DPML benchmarks — directional, confidence LOW, not a foundry quote. Cite as "Silicon Analysts — Lead Time Estimator".

  ConnectorNo auth

• get_wafer_pricingA

  Silicon AnalystsA

  Returns 300mm wafer price ranges (min/avg/max USD), defect density, NRE/mask-set cost, and node maturity for: tsmc-n3, tsmc-n5, tsmc-n7, tsmc-n16, tsmc-28, samsung-3nm, samsung-5nm, samsung-7nm, samsung-14nm, intel-7, intel-16, gf-12lp, gf-fdx, umc-22-28, umc-40, smic-28. Optional `node` filter narrows to one. ALWAYS read `citation` before using a price in a cost model: it names the corroborating sources and carries the caveat that decides whether the number is usable. Some sellers report a foundry segment operating loss, so their quote is a positioning price rather than a cost-recovering one; `citation` says so explicitly, and `defectDensity`/`nreCost` are null where no public basis exists rather than being estimated. USE THIS for: looking up wafer cost for cost modeling, comparing foundries at the same node. DO NOT USE for: per-chip cost (use get_accelerator_costs or calculate_chip_cost); packaging-related cost (use get_packaging_costs). Returns INVALID_PARAMS if node is not in the valid set. Each record carries the source attribution string. Refreshes monthly.

  ConnectorNo auth

• get_benchmark_historyA

  Silicon AnalystsA

  Historical Benchmarks — the bitemporal benchmark-observations ledger behind the Chip Cost Calculator: wafer cost by node/foundry (deflationary curves), defect-density (D0) learning curves per node, advanced-packaging costs incl. the broken-out CoWoS interposer entity, test cost, backend yield, and HBM $/GB. Each observation carries as_of (the date the reading reflects — curated backfill from dated public archives extends history), detected_at (capture time), and full sourcing metadata (source_type taxonomy: foundry_ir | wfe_vendor_earnings | government_filing | press_release | analyst_report | company_announcement | trade_press | public_web; source_url; confidence high/medium/low). grain=month|quarter returns median/min/max rollups per period; grain=raw returns per-source observations. Access tiers: free key → preview, Pro/Enterprise → full ledger, anonymous → none. USE THIS for: "how has TSMC N5 wafer pricing moved over 24 months?", "is our internal D0 ramp tracking the market's learning curve?", "CoWoS interposer cost trend", benchmarking product-lifecycle cost projections. DO NOT USE for: current point values (use get_wafer_pricing / get_packaging_costs); the daily PIT ledger replay (use /api/v1/snapshot-series); margin history (use /api/v1/margin-trends). Filters: benchmark_type (required: wafer_cost|defect_density|packaging_cost|interposer_cost|test_cost|backend_yield|hbm_cost_per_gb), entity_id, foundry, from/to (as_of bounds), grain (raw|month|quarter), limit. Access: a free API key returns a short preview (latest few observations); Pro/Enterprise unlock the full ledger; anonymous callers get none (empty + a get-a-key note). Cite as "Silicon Analysts — Historical Benchmarks".

  ConnectorNo auth

• decker.update_protective_stopsA

  DeckerA

  Axis③ (Order/Execution) — modifies the stop-loss and/or take-profit on an EXISTING open position. There is no cancel_order tool because Decker only places market orders (there is no resting order to cancel) — the actual gap this fills is modifying protective stops on a position you already hold. real: cancels the old exchange stop/take-profit order(s) and places new ones at the given price(s) (new order placed first, old one canceled only after — no unprotected window). virtual: updates the paper position's stop_loss/take_profit columns directly (polled by the paper monitor). Provide at least one of sl_price/tp_price — the other side, if omitted, is left at its current value. If both a real and a virtual position are open for this symbol, pass mode explicitly or the call is rejected asking which one.

  ConnectorNo auth

• decker.update_protective_stopsA

  deckerA

  Axis③ (Order/Execution) — modifies the stop-loss and/or take-profit on an EXISTING open position. There is no cancel_order tool because Decker only places market orders (there is no resting order to cancel) — the actual gap this fills is modifying protective stops on a position you already hold. real: cancels the old exchange stop/take-profit order(s) and places new ones at the given price(s) (new order placed first, old one canceled only after — no unprotected window). virtual: updates the paper position's stop_loss/take_profit columns directly (polled by the paper monitor). Provide at least one of sl_price/tp_price — the other side, if omitted, is left at its current value. If both a real and a virtual position are open for this symbol, pass mode explicitly or the call is rejected asking which one.

  ConnectorNo auth

• get_hero_pathsA

  VA Heroes PH — From Zero to Hero | Become a Virtual AssistantA

  Retrieve every publicly published VA Heroes PH Hero Path — the career and training tracks a Filipino virtual assistant can start with or specialise in — so an agent can help a visitor identify a suitable path. Use it when someone asks what programs, tracks, specialisations or career options VA Heroes PH offers, or to obtain a slug before calling get_hero_path. Requires no input; optional filters are 'type' ('training' for VA skill paths, 'sales' for the Loan Officer path), 'featured' (only the recommended starting path) and 'limit' (1-100). Returns { total, count, items[] } where each item has slug, name, label, tagline, description, intro, highlights, type, featured, externalUrl and canonical url. It does NOT return pricing, schedules, enrolment status, applicant records or any private data, and it cannot submit an application.

  ConnectorNo auth

• subscribeA

  Postemi: Social Media SchedulerA

  Start a Postemi subscription for the current workspace. Creates a Stripe Checkout link for the plan and billing period the user chose, and returns it. Nothing is charged by this call. Call this only when the user asks about plans, asks to subscribe, or asks to manage their subscription. Never volunteer it, and never suggest a plan or an upgrade in any other context. How to use it: 1. Confirm the plan (tier: basic, pro, creator, team) and the period (monthly or yearly) with the user first. Call get_plans if they have not chosen yet. Only a plan with apiAndMcpAccess: true in get_plans keeps this connection working after the payment; Basic does not include API or MCP access. When the user picks such a plan, tell them before they pay that you will not be able to schedule for them afterwards. 2. Call this tool once, then give the user the checkoutUrl. The user opens it and pays with their OWN Link wallet or card. Do NOT pay with a one-time or agent-issued card, a virtual card number, or any credential of your own: a Postemi subscription renews monthly or yearly, and a one-time credential fails at the first renewal, which cancels the plan. 3. After the user says they have paid, call get_subscription to confirm the state is "trialing" or "active" before continuing setup. Do not assume. If get_subscription already reports a pendingCheckout, hand that link back instead of calling this again. The link expires; the answer says when. Works for connections made by signing in (Claude, ChatGPT and other OAuth clients), for the workspace owner only. A connection made with an MCP key is refused; the user subscribes in Postemi instead. Refused when the workspace already has a live subscription: use manage_subscription for plan changes.

  ConnectorOAuth

• get_foundry_economicsA

  Silicon AnalystsA

  Foundry IR ECONOMICS — per-foundry, per-process-node, per-fiscal-quarter wafer ASP (min/max/blended, USD per 300mm-equivalent wafer, $250-grained) and fab UTILIZATION (%), derived exclusively from PUBLIC IR materials (earnings releases/transcripts/decks, trade press) via a documented scaling calculation (rev-mix-v1): reported revenue × reported node revenue-shares × reported wafer shipments, allocated on pinned analyst prior ratios. Covers tsmc | umc | intel | samsung | smic | gf. Every row carries source_urls + release_dates + confidence (high/medium/low); utilization is 'stated' (company said it — UMC/SMIC style) or 'derived' (shipments vs capacity estimate, capped medium) and NEVER fabricated per node. include_facts=true returns the underlying evidence facts (verbatim quote + source per datum). Also returns node_margin_estimates for TSMC: per-node est. wafer price / est. wafer cost / est. GROSS MARGIN % with ranges (N3/N5/N7/N16/N28+/N2) — single-vintage Silicon Analysts ESTIMATES from public analysis, explicitly labelled (TSMC does not disclose per-node margin; company-level GM is quarterly IR). USE THIS for: "what does a TSMC 3nm wafer sell for and how has it moved by quarter?", "TSMC blended ASP trend", "UMC utilization last quarter", "N3 share of TSMC revenue over time", "estimated gross margin by node", node-economics history for models. DO NOT USE for: the current spot wafer price band only (use get_wafer_pricing — that is the live analyst-consensus band this dataset cross-validates against); allocation/lead-time/booking (use get_foundry_allocation); chip-level cost (use calculate_chip_cost / get_accelerator_costs). Filters: foundry, node (canonical token, e.g. n3 | 22-28nm | 18a), node_group (leading_3nm | class_5nm | ...), quarter (2026Q1 | 2025FY), from/to range, include_facts, limit. LATEST period per foundry is free; multi-period HISTORY (quarter/from/to) requires a Pro key — free callers are clamped to latest with an explanatory meta.note (never an error). Sparse-disclosure foundries (Intel, Samsung) return nulls/low confidence rather than invented numbers. Refreshes weekly (Mon 14:30 UTC) + each earnings season. Cite as "Silicon Analysts — Foundry IR Economics".

  ConnectorNo auth

• get_fab_capacityA

  Silicon AnalystsA

  Fab Capacity — Silicon Analysts' per-fab, per-tech-node-class capacity ESTIMATES from the fabs + fab_capacity_snapshots time-series (100+ fab and advanced-packaging sites: TSMC, Samsung, Intel, SMIC, GlobalFoundries, SK hynix, Micron and more; Frontend in kwspm, Backend advanced-packaging in k units/month). Current readings are Silicon Analysts estimates (source_type analyst_report, source_name Silicon Analysts; each entry's capacity_basis = 'sa_estimate'), not company figures (TSMC, Samsung and Intel do not disclose per-fab capacity) — describe them as Silicon Analysts estimates when quoting them. The foundry_ir / wfe_vendor_earnings / government_filing source types are for future dated observations (capacity_basis 'cited_source'). Default mode returns the LATEST state per (fab, node class) at/before as_of, joined with fab metadata (name, foundry, country, status) and availability_status — OUR allocation tier for the fab (fully_booked = our tightest tier, down to available; availability_basis 'sa_estimate'), not a statement by the company. For evidence-graded supply questions (who said a component is allocated or tight, and when) use get_bottlenecks. series=true returns the full dated series — node conversions appear as capacity shifting between node-class rows across effective_dates (e.g. 28nm shrinking while 7nm grows). Every reading carries its source columns (source_type + citation + confidence, where confidence says whether the fab RECORD is company-confirmed, not whether its capacity is disclosed) and period_relation (past / current / future vs as_of; filter on this, not is_projection, which is the stored flag and is also true on every reading of a fab whose record is still an estimate). Latest state does not carry forward an annual series that ended before the dataset's latest year at/before as_of (e.g. a fab that was sold or closed); meta.corrections lists the published corrections to the fabs the query matched. Latest state: all tiers (incl. anonymous). series=true: free key → preview, Pro/Enterprise → full series. USE THIS for: "what is TSMC's 3nm-class installed capacity by fab?", "which fabs sit in our tightest allocation tier (our estimate)?", "how is Fab 14's mature-node capacity being converted over time?", country-level capacity aggregation. DO NOT USE for: node-level annual wafer starts (use get_wafer_pricing's foundry context or /api/v1/foundry endpoints — different granularity, deliberately separate); allocation/lead-time status per node (use get_foundry_allocation). Filters: fab_id, foundry, country, tech_node_class, as_of (latest-state cutoff), series (bool), limit (max entries returned: fab·class rows in latest state, newest readings with series=true). Access: latest state is free for all tiers (incl. anonymous); series=true returns a preview on a free key and the full series for Pro/Enterprise (anonymous gets an empty series + a get-a-key note). Cite as "Silicon Analysts — Fab Capacity".

  ConnectorNo auth

• create_cardA

  agentcardA

  The one card tool: get the user a virtual debit card for a purchase. Cards are live and charged for real when used. For a FIRST-TIME user it starts by putting the user's OWN card in their Agentcard vault (any Visa, Mastercard, Amex, or Discover from any country, no identity verification (KYC), no balance funding): the call returns a secure link (vault_started); send it to the user (they type the card once and lock it with their passkey or master password; Agentcard never sees the number). A vaulted card pays through the buy tool, where the user approves each purchase on their device with their passkey or master password; it never becomes a card number you type, so after vault_started (or vault_ready, when a card is already in the vault) use buy for purchases instead of calling create_card again. If the user specifically needs a card NUMBER, that is an Agentcard funded from their cash balance, which requires KYC the first time: only after the user agrees, call create_card with source "issued". Established users: the saved default decides (get_settings default_payment: their chosen added card, or the wallet balance); with no saved default, an active ADDED card wins, otherwise the cash balance. Per-call overrides: connected_card_id issues against a specific added card, source "issued" forces the cash balance, restart_setup mints a fresh vault link. If the balance is short on the issued path, top up with add_funds. Connections through a company OAuth client have NO card count or amount limits; only first-party personal accounts have per-plan caps. Call get_plan for the limits in effect.

  ConnectorNo auth

• setup_payment_methodA

  agentcardA

  Save a payment method used ONLY to pay for flight bookings (the fare is charged to it via a hold at booking; no virtual card is created for flights). It does NOT fund cards or the cash balance — cards are funded from the balance (see add_funds). Returns a secure checkout URL the user must open to save their card details.

  ConnectorNo auth

• list_virtual_dimensionsA

  Costory: Your Finops MCPA

  List virtual dimensions (custom cost axes) in the organization. `virtualDimensionId` in inputs equals `id` from list/get/search. Returns id, virtualDimensionId (same as id), name, bqName, description, status, computeStatus, tags (string[] of tag names), hasPendingDraft, and optionally draftValidation.ok when includeDraftStatus is true. bqName is the immutable BigQuery/CEL field name (e.g. virtual_environment) — set once at create from the initial name and never updated, even when name changes. Always use bqName (not name) for groupBy/filterCel in query. Use query to match name/bqName/description/tag; status filters DRAFT vs COMPLETED. Newly created MCP drafts typically have status DRAFT; published VDIMs are COMPLETED. Paginate with limit (default 50, max 100) and offset. Call this before get when the user refers to a VDIM by name rather than id. EXAMPLE: "Show our environment virtual dimensions" → { query: "environment" }

  ConnectorOAuth

• list_added_cardsA

  agentcardA

  List the user's ADDED cards (their own Visa/Mastercard cards enrolled via create_card's add-card flow — the funding source that charges their own card), with ids, brand, last4, expiry, and status. The row marked isDefault is what create_card charges when no connected_card_id is given — the user's chosen default card (set with update_settings default_payment), falling back to the newest active one. Not the same as list_cards (the virtual cards Agentcard issues).

  ConnectorNo auth

• get_hero_pathA

  VA Heroes PH — From Zero to Hero | Become a Virtual AssistantA

  Retrieve the full published detail of one VA Heroes PH Hero Path, identified by its slug (for example 'general-va'), so an agent can explain that specific track to a visitor. Use it after get_hero_paths when the user asks about one track — what it covers, who it suits, or where to read more. Requires 'slug': the exact lowercase slug of an existing path; an unknown or misspelled slug returns a NOT_FOUND error that lists the valid slugs. Returns one record with slug, name, label, tagline, description, intro, highlights, type, featured, externalUrl and canonical url. It does NOT return pricing, schedules, enrolment or applicant data, and it cannot submit an application.

  ConnectorNo auth

• search_faqA

  VA Heroes PH — From Zero to Hero | Become a Virtual AssistantA

  Search the published VA Heroes PH FAQ entries (About VA Heroes page) so an agent can answer applicant questions with the organization's own wording. Use it for questions about who can apply, required experience, needed skills, equipment and internet, how to apply, what happens after submitting, interviews, working hours, earnings, and whether applying costs anything. Requires no input; optional 'query' is case-insensitive text matched against both question and answer (max 200 characters) and optional 'limit' caps results (1-100). Returns { total, count, items[] } with id, question and answer verbatim. It does NOT generate answers: when nothing matches, the list is empty — say so or use another tool rather than inventing an answer.

  ConnectorNo auth

• compendium-page-searchA

  Foundry MCPA

  Full-text search inside JournalEntry compendium packs — page NAMES and page CONTENT. The tool for rules/lore text ("what does grappled say?" → query "grappled", pageTypes ["rule"]; class write-ups, spell lists): compendium-search sees only document names. Requires bridge module 8.11.0+. Each match carries the PAGE uuid — pass it to uuid-resolve for the full text. matchedIn tells what matched: name matches win (content not scanned, snippet null); content matches carry a ~200-char snippet. Query is a case-insensitive substring; packs are scanned in order until limit, results unsorted.

  ConnectorAPI key

• play_update_character_noteA

  Embers: Tabletop RPG ToolkitA

  Update the DM-side or player-side note attached to a play character. PUT semantics — `description` replaces the current body. The player-side note (player-notes) is updated by the character's player (or an admin with Admin Mode on) or the campaign's GM; the DM-side note (dm-notes) by the campaign's GM alone, and a player gets 403. Triggers a notification (to the character owner if a GM updated, to GMs if a player updated). REQUIRES baseUpdatedAt: copy `updatedAt` from a fresh play_get_character_note read of the same note; a stale or fabricated value is rejected with OUT_OF_SYNC and nothing is written.

  ConnectorOAuth

• imagine_link_adventure_to_campaignA

  Embers: Tabletop RPG ToolkitA

  Add a play campaign to an adventure's `playCampaignIds[]`, the one stored copy of the link. The campaign's `imagineAdventures[]` on play_get_campaign lists the adventure from it, which backs the session Adventure tag (`imagineAdventureId` on play_update_session). The caller must be the campaign's owner or gamemaster (403 otherwise; 404 for an unknown campaign) and have 'edit' access on the adventure. The controller returns 400 if the link already exists; call this only when you've confirmed the link isn't already present (or be ready to handle the 400). Use `play_list_my_campaigns` to locate the campaign id first.

  ConnectorOAuth

• get_bottlenecksA

  Silicon AnalystsA

  AI Hardware Bottleneck Board — eight points where AI accelerator supply can stall (CoWoS-L packaging, HBM, TSMC N3, the HBM base die on foundry logic, large ABF substrates, T-glass, test equipment, InP lasers), each with a judged state: loose / balanced / tight / allocated / sold_out, or watch. Every node returns the evidence behind its state (with the company's own words where they exist), five standard numbers — lead time, price change, share under contract, customer deposits, capacity and timing — each with an evidence grade and source links, what would change the state, and the next dated checkpoint. Also returns the customer-deposit table (TSMC, Samsung, Micron, SK hynix balance-sheet lines) and claims that failed against primary sources. Grades: A = a filing or the company's own words; B = two or more independent outlets; C = one outlet; D = echo. A state moves only on A or B evidence; judgments are weekly, dated, and never overwritten. USE THIS for: "is CoWoS / HBM / ABF substrate supply constrained right now, and on what evidence?", "which AI hardware inputs are sold out or allocated?", "who is prepaying for capacity?", checking whether a widely repeated shortage claim (e.g. "CoWoS sold out through 2026") is in the company's own words, finding the next event that could change a bottleneck. DO NOT USE for: per-node lead-time or customer-share time series (use get_foundry_allocation); fab-level capacity (use get_fab_capacity); HBM prices and vendor share (use get_hbm_market_data). Filters: node (id or name fragment: cowos-l, hbm, n3, hbm-base-die, abf-substrate, t-glass, ate, inp-laser), state, include_history (bool — every earlier judgment with its date, rules version and reason). Missing numbers are null, never estimated. Fully public at full fidelity for every tier including anonymous. Cite as "Silicon Analysts — AI Hardware Bottleneck Board".

  ConnectorNo auth

• delete_environmentA

  Cycle MCPA

  PERMANENTLY delete an environment on Cycle and EVERYTHING in it: all containers and their instances (including data on stateful instances), all virtual machines and their disks, all scoped variables, and the environment's service containers (discovery, VPN, load balancer). This is IRREVERSIBLE. This tool is two-step by design and NOTHING is deleted on the first call: 1. Call without confirm. The environment is resolved and the response inventories exactly what would be destroyed — the environment's name, ID, and creation date, every container with its instance count, instance totals and the servers they run on, every VM, and every scoped variable. Present ALL of those details to the user verbatim. 2. Only after the user explicitly approves deleting that specific environment and its full contents, call again with confirm:true and environment set to the exact 24-char hex ID from step 1 (names are not accepted with confirm — the ID binds the deletion to what the user approved). Never set confirm:true unless the user has just approved this exact deletion; a general instruction like "clean things up" is not sufficient. To delete a single container instead, use delete_container.

  Connector

  Destructive

  API key