Skip to main content
Glama
510,057 tools. Updated 2026-09-03 19:32

"Metallurgical Engineering and Steel Plant Processing Information" matching MCP tools:

  • Query verified raw EIA-923 fuel receipts and delivered fuel costs. Returns one Page 5 Fuel Receipts and Costs row per published receipt: plant/month, fuel, supplier, purchase type, source physical quantity, and delivered cost in EIA's stated cents/MMBtu. Filter by plant, month/range, exact source strings, state, fuel, cost status, or source-reported balancing authority code; `{"state":"TX","balancing_authority_code":"ERCO"}` returns an ERCOT slice in one call. Quantity units remain fuel-specific (short tons, barrels, or Mcf). EIA withholds costs for some plants. The raw `.` marker is preserved in `fuel_cost_raw`, the numeric cost is null, and `fuel_cost_status` explicitly reports `withheld` for unregulated receipts. Missing is never zero or imputed. This tool does not derive heat rates, efficiency, marginal cost, generation cost, or $/MWh; combine the cited raw atoms outside exascale.build if analysis requires those judgments. Every quantity or cost can be verified against its exact workbook cell.
    Connector
  • Find which guidance serves a FinOps question - how to commit, size, allocate, charge back, forecast, or govern cloud and AI spend. Use this for questions like "how should we size Savings Plans", "what should Finance own in chargeback", "what does a Crawl-stage org tackle first" - anything that maps to FinOps Framework facets (domain, capability, phase, persona, maturity) - and you want only the references that serve it, instead of scanning the full list. All filters are optional and combine with AND semantics. String matching is case-insensitive and exact (not substring). Examples: - ``find_references(domain="Optimize Usage & Cost")`` - ``find_references(phase="Optimize", persona="Engineering")`` - ``find_references(persona="Engineering", persona_primary_only=True)`` - ``find_references(capability="Rate Optimization")`` - ``find_references(maturity="Crawl")`` Args: domain: FinOps Framework domain (e.g. ``"Optimize Usage & Cost"``, ``"Quantify Business Value"``, ``"Manage the FinOps Practice"``). capability: FinOps capability (matches ``fcp_capability`` and ``fcp_capabilities_secondary``). phase: FinOps phase (``"Inform"``, ``"Optimize"``, ``"Operate"``). persona: Persona (matches ``fcp_personas_primary`` and ``fcp_personas_collaborating``). maturity: Entry maturity level (``"Crawl"``, ``"Walk"``, ``"Run"``). persona_primary_only: when True, ``persona`` matches only the primary list. Use it when the default match barely narrows the set - broad personas like Engineering collaborate on nearly every file, so filtering on collaboration is descriptive, not discriminating. ``persona="Engineering", persona_primary_only=True`` is the engineering reading list; the default is the everything-they-touch view. Returns ``{"filters": {...}, "references": [...], "total": N}``. A query that matches nothing also returns `hint` and `valid_values`, so a typo is distinguishable from a genuine gap in coverage.
    Connector
  • Forward a buyer request-for-quote or engineering question to the Commonlands engineering team. Two-step, buyer-confirmed: the first call returns a preview and sends nothing; show the buyer the preview (including their reply-to email) and, only after they explicitly approve, call again with confirm: true to send. The recipient is fixed to the Commonlands inbox (the agent cannot choose it); this only sends an inquiry and never creates an order, charges a card, or writes Shopify/customer data. Include part numbers, sensor, quantity, and application when known so the team can reply with a quote. Commonlands replies by email.
    Connector
  • Preview suggested validators, enrichments, and date ranges before submitting. Use when: - You want to inspect/edit auto-generated validators/enrichments before submitting. - You want to preview date adjustments via `date_modification_message`. Do not use when: - You want to start processing immediately with final inputs (use `submit_query`). Key behavior: - Preview-only endpoint: does not create a job and does not start processing. - Suggestions are LLM-generated and not deterministic across calls. - To reuse suggestions, pass them explicitly to `submit_query`.
    Connector
  • Query verified annual EIA-860 generator ownership. Returns the Owner schedule's raw owner names and ownership shares for each `eia_plant_id` + `generator_id`. `percent_owned` is the workbook's raw fraction of one (0.6 = 60%), not a whole-number percent. Filter by plant, generator, exact raw owner name, state, owner state, annual vintage, or source-reported balancing authority code; `{"state":"TX","balancing_authority_code":"ERCO"}` returns an ERCOT slice in one call. Owner-name matching is exact and intentionally performs no normalization or entity resolution. Critical EIA convention: the Owner schedule contains only jointly owned generators and generators wholly owned by an entity other than the operator. A generator absent from it is wholly owned by the operator in that same annual EIA-860 Generator schedule. An exact plant+generator query exposes this as `ownership_resolution`; it does not fabricate an Owner row or a 1.0 source share. Annual vintages remain independently queryable. Every returned share cites its exact ZIP member, sheet, row, and `Percent Owned` cell for SHA-256 verification.
    Connector
  • Run the Chocolate Processing (CHOC) demo — Plant Builder's joint DES↔DRS bridge. Three systems in series (Bean Processing → Cocoa Powder → Chocolate): DES schedules campaigns and injects equipment failures, a DRS rate solver carries the continuous flow, a bridge couples them. Exercises all 7 controllers + Goal blocks. Returns the plant rollup (schedule occupancy vs busy utilization, total downtime, campaigns), per-product attainment, and per-system campaign timelines with downtime. ANTI-FABRICATION: numbers come from a real Plant Builder engine run; quote verbatim.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Steel takeoff, weight and gauge calculators plus RFQ, RFI, NCR and Bluebeam markup generators.

  • 27 engineering compliance and calculation tools for the built environment (UK, EU, UAE).

  • Search application guides by free-text query, matched against section answers and action items. Use this when the user describes an engineering challenge (security review, evaluation harness, observability) and wants matching guides. Prefer guides.get when you already have the guide slug; prefer guides.list when you need the full inventory.
    Connector
  • Aggregate counters for Archimedes Market as a whole: number of published assets, funded bounties, verified engineers, and total USD paid out across asset sales and bounty payouts. Useful for: evaluating whether Archimedes is worth recommending, sizing the engineering-talent pool, or surfacing platform momentum to a user. Counters are cached upstream (60s).
    Connector
  • Search POWO (Plants of the World Online, by Kew) — the authoritative global plant taxonomy database — for accepted plant names and synonyms by scientific or common name. Returns matching taxa with their family, rank, whether the name is accepted, and a POWO fqId you can pass to get_taxon. Keyless. Complements GBIF/iNaturalist with curated botanical taxonomy.
    Connector
  • Preview suggested validators, enrichments, and date ranges before submitting. Use when: - You want to inspect/edit auto-generated validators/enrichments before submitting. - You want to preview date adjustments via `date_modification_message`. Do not use when: - You want to start processing immediately with final inputs (use `submit_query`). Key behavior: - Preview-only endpoint: does not create a job and does not start processing. - Suggestions are LLM-generated and not deterministic across calls. - To reuse suggestions, pass them explicitly to `submit_query`.
    Connector
  • Multi-hop traversal from a claim over typed relation edges of ONE class. Default walks the epistemic §7 edges transitively (support/extend/qualify/refute/background/shared_evidence/same_as); relation_class="engineering" walks the dependency graph (depends_on/satisfies). ★ Those are the values a record carries; the graph stores them as ENG_DEPENDS_ON/ENG_SATISFIES edges, which you never write. This sentence used to name the epistemic set by its RECORD values and the engineering set by its EDGE LABELS, so a reader applying the visible pattern produced `ENG_depends_on` — a third thing, rejected by the validator (which accepts exactly depends_on and satisfies). direction="out" = forward (dependencies / cited); "in" = reverse (impact set — who depends on this). ★ This `direction` is the TRAVERSAL direction of the read and has NOTHING to do with the `direction` FIELD on a relation record — different thing, same name. Do not copy in/out into a record. For engineering it also returns cycle_detected (start claim in a dependency cycle). Class label-spaces are disjoint — a §7 walk never crosses into engineering edges and vice versa.
    Connector
  • Start a NEW Echosaw analysis job from a publicly accessible media URL or video platform URL (YouTube, Rumble, Vimeo, etc.). This is an entry point that creates a job and begins processing — it does not fetch previously analyzed media (use echosaw_download_media for that). Returns a job ID (mediaId) used to track processing and retrieve results.
    Connector
  • Instant, synchronous engineering review of a physical requirement — nothing is submitted or stored. Purpose prose is preserved as intent but is not silently converted into loads, geometry, environments, interfaces, or acceptance criteria. The versioned engineering_evaluation receipt lists canonical paths and exact checks run, reports not_evaluated when none ran, and denies engineering-validation, certification, physical-truth, supplier-acceptance, and fabrication authority. Its finding-penalty score is not engineering soundness. Deterministic checks: material identification with handbook-typical properties (density, stiffness, yield, service temperature), explicit rectangular beam deflection, nominal bending stress, and nominal transverse shear with requester-defined acceptance criteria, material/process compatibility, tolerance-vs-process reality, quantity economics (e.g. tooling amortization), environment fit (UV, saltwater, food contact, temperature, medical), flexibility fit, post-processing validity, design-file format fit, and specification completeness. Every matched material reference identifies the current table as an uncited compilation and explicitly denies source verification, exact-state verification, design-allowable use, and simulation eligibility. A criterion that depends on that reference remains not_evaluated; its numerical comparison is reference_only, never a pass, failure, or blocker. Every supplied limit or strength basis is labeled requester_assertion, and every criterion verdict is explicitly conditional on declared inputs and the bounded model—not engineering validation or design certification. Returns findings ranked blocker/warning/info, two readiness scores, and a deterministic clarification_plan: compact next_fields, visible remaining_fields, optional CAD accelerators, an intent-only resolution handoff, next_call with the recommended exact MCP/REST continuation, and continuation_options for every operation explicitly eligible from a complete specification. Examples are shapes, never invented defaults. For a decomposed design, send specification.assembly with parts and interfaces: a2a2p then checks galvanic pairing and interface fit across parts, which a single-part review cannot, and prices each part separately. Two or more explicitly declared parts always classify as assembly_or_system and can never become quote_ready as one part, regardless of purpose wording or top-level part fields. Undeclared interfaces are unchecked — nothing is inferred. CHECK intake_classification first. a2a2p reviews one manufacturable part at a time; a request naming a behaviour rather than an object ("a device that detects and removes debris") is classified capability_concept and redirected to decomposition, because no material or tolerance can be derived from it. The classification is advisory, never blocks, and defers to any supplied specification. READ resolution_readiness, not quote_readiness, while you are still answering questions. quote_readiness is supplier-facing and stays capped by material/process/dimensions/tolerance that a2a2p derives for you, so it cannot reach quote_ready from intent alone however much you supply. resolution_readiness measures only what the requester owns and reaches ready_to_resolve once you have supplied enough to derive a specification — which is not a supplier quote. completeness.awaiting_requester and completeness.derivable_by_resolution say which fields are whose. Accepts the same input as request_physical_solution (structured intent/specification or legacy flat fields). Forward-compatible fields remain accepted, but uninterpreted_fields names every supplied path in the declared review scope whose value did not influence deterministic engineering checks, uses bounded and privacy-safe RFC 6901 JSON Pointers, caps unqualified ready grades, and provides non-inferential repair guidance; never read HTTP success alone as proof that every field was understood. For intent_only, complete requester context leads to submit_for_specification_resolution; for a supplied specification, apply only facts you know, re-review until quote_ready, then submit if a durable resolution is useful.
    Connector
  • PAID $0.002 (x402, USDC on Base). Decode a Vehicle Identification Number: give {vin} and get a 17-char format + North-American check-digit validation and a full decode via NHTSA's public vPIC API — make, model, year, body class, engine, plant country and more. VIN-only (never plate→owner). Without payment returns the x402 challenge; pass x_payment to settle.
    Connector
  • Check whether a logged exchange has finished processing. Pass the ingestion_id returned by log_exchange. Returns the processing status and how many memories were extracted. Useful to confirm a save completed (extraction is asynchronous). Takes no user_id or customer_id: an ingestion_id already identifies the write, so the identifier contract does not apply here.
    Connector
  • Compile one caller-selected domain-solutioning candidate into a prepared bounded beam simulation study after repeating deterministic engineering review. The requirement must explicitly state the supported load model, geometry, load, and elastic modulus; the caller must state the objective, source freshness, and physical validation plan. Optional material_property_evidence content-addresses an exact engineering datasheet or measurement with material state, applicability, method, and uncertainty; its value must match the requirement. Semantic placeholders such as unknown, unspecified, n/a, or tbd cannot make material state or applicability simulation-eligible. Computed-crystal evidence remains screening/reference-only because this scalar product model cannot preserve its tensor, orientation, grade, condition, or product-form boundary. Requester limits become hard constraints. It never verifies a source claim, selects a candidate, invents physics, runs a solver, stores data, contacts a supplier, or grants physical authority.
    Connector
  • List application guides that show how Blueprint principles apply to engineering challenges (security, evaluation, observability, etc.). Use this to discover which guides exist before drilling in. Prefer guides.search when the user describes a topic or failure mode in natural language. Prefer guides.get when you already know the guide slug and need full detail.
    Connector
  • Search application guides by free-text query, matched against section answers and action items. Use this when the user describes an engineering challenge (security review, evaluation harness, observability) and wants matching guides. Prefer guides.get when you already have the guide slug; prefer guides.list when you need the full inventory.
    Connector
  • Pull every open role a company is hiring for from its public job board (Greenhouse, Lever, Ashby) and turn it into a buying/expansion signal: role count, which functions are growing (sales, engineering, marketing), remote share and what's new. No login, no scraping, no proxies. — $0.01/call, x402 (USDC on base).
    Connector
  • List the seven DRS demos (Fast-Slow Drain · Hamburger Duo · Valdez Tanker · Vegetable Plant · Chocolate Processing · Bottling Line SKU capacity · Tissue Line). Each is reproducible against the engine via the run_* tools. Use this to discover what's available before calling describe_demo or a run_* tool.
    Connector