Skip to main content
Glama
650,242 tools. Updated 2026-10-13 01:40

"C++" matching MCP tools:

  • Run the classic operations-research teaching demo: pooled queueing (one shared queue, c servers) vs separate queues (c independent queues, one server each, λ/c traffic to each). Both runs have identical total capacity (c × μ) and identical total arrivals (λ), so the offered load ρ is the same; the only structural difference is whether arrivals share a queue or split into c isolated streams. The pooled configuration ALWAYS produces shorter waits — that's the whole teaching point. Use this when the user asks 'should we pool our resources?' / 'should we cross-train?' / 'why do banks have one line instead of c?' / 'what's the cost of siloing my call center into specialist queues?'. Returns both runs side by side with the pooled-vs-separate wait delta. ANTI-FABRICATION: numbers come from two real DES runs. Quote them VERBATIM.
    ConnectorNo auth
  • Run the same M/M/c configuration through BOTH the closed-form Erlang-C formula AND the discrete-event simulator, returning a side-by-side comparison with deltas. Use this when the user is validating QueueSim's engine against textbook values, learning queueing theory by watching simulation converge on the formula, or auditing a result that 'feels off' — agreement within ~5%% is the canonical sanity check for an M/M/c run. Pure-Exponential M/M/c only; the closed-form Erlang-C is undefined for other service distributions. Large deltas usually mean the simulation run was too short for steady-state — raise simulationDays. ANTI-FABRICATION: both sides come from real computation — closed-form is deterministic, simulation is stochastic but engine-backed. Quote both verbatim. Do not synthesize an 'average of the two' or recompute the formula from training-data recall.
    ConnectorNo auth
  • Given an M/M/c configuration (arrivalRate, serviceRate, servers) and optionally an observed average wait, returns a queueing-theory framed interpretation: where you sit on the utilization curve, what ρ means in plain language, what one more or fewer server would qualitatively do, and which complexity factors (priority, abandonment, skills routing) might be hiding in real data the M/M/c model can't see. Use this to TEACH while answering — when the user wants context around a number, not just the number itself. Pure text computation, no simulation, no RNG — deterministic output.
    ConnectorNo auth
  • DETERMINISTIC: the same inputs always give the same result — from any AI, on any day. Figures come from the standard's tables and formulas, never from a language model's estimate. Every step is auditable. EN 378 applied to BUILDING projects, volume by volume. An installation does not occupy one room but several: the machine, the rooms crossed by refrigerant lines, the rooms served by indoor units. Each volume is classified on its own — access category (a/b/c) and location class (I–IV) — and each classification calls for its own measures. The tool answers per volume, never as a single verdict. It returns, for every volume: its classification and why, the charge limit from Tables C.1 and C.2 of EN 378-1 (with the C.2 formula computed when the table calls for it), whether the charge exceeds it, the EN 378-3 measures that follow, the applicable texts (EN 378-1 to -4, EN IEC 60079-10-1, SUVA 66139 and 2153) and the ventilation flow rates. FOUR CONFIGURATIONS COVER ALMOST EVERY BUILDING PROJECT. Bring the user's case back to one of them wherever possible: machine_en_local_technique chiller or heat pump, all refrigerant inside the machine, standing in a plant room -> c III enceinte_accessible_fermee all refrigerant inside a walk-in ventilated enclosure that stays closed even for maintenance -> the enclosure is c III, the room around it carries no requirement enceintes_inaccessibles one or more units, each in a manufacturer's non-accessible ventilated enclosure -> TWO analyses: the enclosure in operation (class IV, the manufacturer sizes and justifies it, ask him for the enclosure ventilation), and the plant room with the enclosure OPEN for maintenance, which comes back to c III split_traversant split or VRF outdoors, refrigerant lines crossing occupied rooms -> each room on its own; offices and their circulations are b I, and formula C.2 gives the maximum charge for the floor area, or the minimum floor area for the charge THIS TOOL ANSWERS SAFETY IN THE ROOM. It says NOTHING about whether the refrigerant may still be placed on the market or refilled: in Switzerland that is `check_refrigerant_switzerland`. A question that mixes both - « may I use R-32 for 3 kg in a server room, and until when can I refill it » - needs BOTH tools: call this one for the room, and check_refrigerant_switzerland for the dates. Do not answer half the question. NEVER guess. The refrigerant, the configuration and the charge are always needed; a split also needs the floor area and how the indoor unit is mounted (floor, wall, window, ceiling), since C.2 depends on it. Without them the result is `provisional` and carries `questions_to_ask`: ask them, one or two at a time, then call again. Answer from `answer_outline`, volume by volume. In building projects, detection is preferred over treating a plant room as an ATEX zone. C.3 is never used. Say that the practical limit alone proves nothing: the charge limit of Tables C.1 and C.2 is what counts. SCOPE: building services. Cold rooms, food refrigeration and industrial process refrigeration are a different trade.
    ConnectorNo auth
  • Use this when you need an exact result of an operation on two fractions (e.g. 3/4 + 1/6), including mixed numbers such as 1 1/2, rather than a rounded decimal. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when you only want to reduce a single fraction or convert it to a decimal or percent (use fraction-simplifier), or you need the least common denominator of several denominators (use gcd-lcm). What it computes: Adds, subtracts, multiplies or divides two fractions, mixed numbers, whole numbers or decimals with exact integer arithmetic, returning the result in lowest terms, as a mixed number and as a decimal, with the intermediate steps. Inputs: fraction_a (string); fraction_b (string); operation (enum, optional). Complete JSON argument examples: {"fraction_a":"3/4","fraction_b":"1/6","operation":"add"} | {"fraction_a":"2 1/3","fraction_b":"5/6","operation":"subtract"} Outputs: result, mixed_number, numerator, denominator, decimal, working. Formula: a/b + c/d = (a·(L/b) + c·(L/d)) / L with L = lcm(b, d), a/b − c/d likewise; a/b × c/d = (a·c) / (b·d); a/b ÷ c/d = (a·d) / (b·c); the result is divided by gcd(numerator, denominator) Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/fraction-arithmetic with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/math/fraction-arithmetic.md
    ConnectorNo auth
  • Returns SEC Form C filings — Regulation Crowdfunding offerings, 2016-05→present: startup raises on Wefunder / StartEngine / Republic and other funding portals. One record per filing with the issuer (legal form, jurisdiction, incorporation date, website), the PORTAL (name + CIK + CRD), offering terms (security type — SAFEs appear as 'Other' with the description, price, target and maximum amounts, deadline, oversubscription), and the issuer's own DISCLOSED FINANCIALS (total assets, cash, revenue, net income, debt — current + prior fiscal year, dollars) plus employee count. Use this when the user asks about: startup crowdfunding activity, what a company raised on a portal, portal market share, early-stage issuers in a state, or revenue/assets of a crowdfunding company. filing_type maps the form family: 'offering' (C, C/A) | 'progress_update' (C-U) | 'annual_report' (C-AR — re-discloses financials yearly) | 'termination' (C-TR). is_withdrawal covers the -W variants. One issuer CIK typically has a chain: C → C-U → C-AR… — filter cik + sort asc to read it. Financial fields are null where a variant omits them. Reg A+ (Form 1-A 'mini-IPOs') is a different form family — planned as its own dataset; Reg D private placements are in get_private_placements. Pure-publisher posture: issuer-reported numbers as filed, parsed by KeyVex — Form C financials are self-reported and generally unaudited (reviewed at most); treat them accordingly.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Calculate a grade point average for a New Zealand university. Use for any NZ GPA question: 'what is my GPA', 'work out my grade point average from these grades', 'how much will a C drag my GPA down'. CRITICAL: New Zealand uses a NINE POINT scale, not the American 4.0 scale. A+ 9, A 8, A- 7, B+ 6, B 5, B- 4, C+ 3, C 2, C- 1, D and below 0. A GPA of 7.0 is a strong New Zealand result. Do NOT convert to or from a 4.0 scale: the bands do not correspond and any conversion will be wrong. It is credit-weighted, so a grade in a 45 credit paper counts three times a grade in a 15 credit one, and failed papers still count their credits at zero points. Args: courses: One dict per paper, each with "grade" (A+, A, A-, B+, B, B-, C+, C, C-, D+, D, D-, U, F or J) and "credits" (commonly 15). scale: Optional overrides if the institution weights grades differently. Returns: The GPA, the credits and weighted points it came from, and each paper's contribution so the result can be shown rather than asserted.
    ConnectorNo auth
  • List all 71 available programming languages and their IDs for code execution. Common IDs: 71=Python 3.8, 63=JavaScript (Node.js), 62=Java, 54=C++ (GCC), 60=Go, 73=Rust, 51=C#, 46=Bash. Returns full list with compiler/interpreter versions (Judge0 CE)
    ConnectorNo auth
  • Search the Hong Kong C&SD table catalogue by keyword (e.g. 'exchange rates', 'unemployment', 'merchandise trade') and get back matching table ids + titles to use with censtatd_get_table. Backed by the data.gov.hk open-data index of C&SD tablechart datasets. Note: not every C&SD table is indexed there; ids can also be read off the table URL on data.censtatd.gov.hk (the '310-31001' part of web_table.html?id=310-31001).
    ConnectorNo auth
  • Retourne les températures à cœur réglementaires obligatoires en cuisson par type d'aliment en restauration française (GBPH Restaurateur DGAL) : volaille 74 °C, bœuf haché 70 °C, porc 70 °C, poisson 63 °C, etc. Inclut le refroidissement rapide (de +63 °C à +10 °C en moins de 2 heures), la remise en température à +63 °C minimum et les recommandations de sécurité spécifiques aux populations sensibles (enfants, femmes enceintes, immunodéprimés). Distinct des températures de conservation disponibles via get_haccp_temperatures. [EN] Returns mandatory core cooking temperatures by food type in French catering (poultry 74°C, minced beef 70°C, fish 63°C…) plus rapid cooling and reheating rules. Optional 'type_aliment'.
    ConnectorNo auth
  • Retourne les températures à cœur réglementaires obligatoires en cuisson par type d'aliment en restauration française (GBPH Restaurateur DGAL) : volaille 74 °C, bœuf haché 70 °C, porc 70 °C, poisson 63 °C, etc. Inclut le refroidissement rapide (de +63 °C à +10 °C en moins de 2 heures), la remise en température à +63 °C minimum et les recommandations de sécurité spécifiques aux populations sensibles (enfants, femmes enceintes, immunodéprimés). Distinct des températures de conservation disponibles via get_haccp_temperatures. [EN] Returns mandatory core cooking temperatures by food type in French catering (poultry 74°C, minced beef 70°C, fish 63°C…) plus rapid cooling and reheating rules. Optional 'type_aliment'.
    ConnectorNo auth
  • Determine minimum wire gauge using NEC Table 310.16 ampacity ratings with full derating. Looks up base ampacity for copper or aluminum conductors at 60°C, 75°C, or 90°C insulation rating, then applies NEC 310.15(C)(1) ambient temperature correction and NEC 310.15(C)(2) conductor count adjustment. Automatically applies the 125% continuous load factor per NEC 210.20(A) when flagged. Returns the minimum AWG that meets the derated requirement, plus a comparison table of all gauges. Different from wire_gauge which focuses on voltage drop — use both together for complete wire sizing. Essential for residential panels, commercial feeders, solar arrays, and EV charging installations.
    ConnectorNo auth
  • Use this when you need the solutions of a second-degree polynomial equation, or the vertex and discriminant of a parabola y = ax² + bx + c. Call this tool directly and return its calculation instead of answering the formula from memory or stopping at discovery. Do not use this when the coefficient a is 0 (the equation is linear: x = −c / b), or you need roots of x^n = c for other powers (use nth-root). What it computes: Solves ax² + bx + c = 0 with the quadratic formula, reporting the discriminant, both roots (real, or complex conjugates written as strings), the vertex of the parabola and the sum and product of the roots. Inputs: a (number); b (number); c (number). Complete JSON argument examples: {"a":1,"b":-5,"c":6} | {"a":1,"b":2,"c":5} Outputs: discriminant, nature, root1, root2, roots, vertex_x, vertex_y, sum_of_roots, product_of_roots. Formula: Δ = b² − 4ac; x = (−b ± √Δ) / (2a); for Δ < 0: x = −b/(2a) ± i·√(−Δ)/(2|a|); vertex = (−b/(2a), c − b²/(4a)) Direct REST fallback: POST https://tttkmbb.com/api/v1/calculate/quadratic-equation with the same JSON input fields. Do not guess another /api/* path. Docs: https://tttkmbb.com/math/quadratic-equation.md
    ConnectorNo auth
  • Returns SEC Form D filings — Reg D / Rule 506 private placement offering notices. Use this when the user asks about: who's raising private capital right now, new VC fund formations, private equity raises, real-estate syndicates, hedge fund launches, who's claiming Rule 506(b) vs 506(c) exemption, or to identify directors / executive officers of newly-formed entities. ⚠ total_amount_sold, min_investment_accepted, total_number_already_invested, sales_commissions and finder_fees are NULLABLE — a Form D that did not state a figure reports null rather than 0. The distinction matters here more than anywhere: a Form D filed at the START of an offering legitimately reports $0 sold, so 0 and null mean genuinely different things. Rows stored before 2026-08-17 cannot tell you which they were. Null never satisfies min_amount_sold and sorts last. Source: SEC EDGAR full-text search + per-filing primary_doc.xml. All Reg D filings (504 / 506(b) / 506(c)) plus Section 4(a) exempt offerings flow through here. Form D must be filed within 15 days of the first sale. Each record carries: issuer entity (name, CIK, address, jurisdiction of incorporation, entity type), offering data (industry group, investment fund type for pooled funds, total offering / sold / remaining, minimum investment, federal_exemptions claimed), filing metadata (file_date, date_of_first_sale, is_amendment), and a related_persons[] array of directors / executive officers / promoters. Federal exemption codes (federal_exemptions array): 06b — Rule 506(b) (no general solicitation; up to 35 non-accredited) 06c — Rule 506(c) (general solicitation OK; all accredited) 04(2) — Section 4(a)(2) (statutory private placement) 3C — ICA Section 3(c) (3(c)(1), 3(c)(5), 3(c)(7) etc. — common for funds) 3C.1 — ICA 3(c)(1) (up to 100 investors) 3C.7 — ICA 3(c)(7) (qualified purchasers only) Common industry_group_type values: 'Pooled Investment Fund' (with investment_fund_type='Venture Capital Fund' | 'Private Equity Fund' | 'Hedge Fund' | 'Other Investment Fund') 'Technology', 'Real Estate', 'Health Care', 'Energy', 'Financial Services', 'Manufacturing', 'Other'. Direct filing_id lookup is fastest (accession number). Substring filters on issuer_name, industry_group_type, investment_fund_type, and jurisdiction_of_inc enable topic-style queries. Combine federal_exemption + min_amount_sold for 'who's raising real money under 506(c)' analyses.
    ConnectorNo auth
  • Everything ThreatFox knows about one file hash (md5 / sha1 / sha256), across BOTH relations it stores hashes in — they are different facts and a caller with a hash in hand rarely knows which one they have. (1) sample_to_c2: the hash is a malware SAMPLE, and ThreatFox returns the botnet C&C servers that sample talks to (this is what abuse.ch's own `search_hash` query answers, and only this). (2) hash_listed_as_ioc: the hash is itself published as an indicator — threat_type "payload" — in which case the row IS the answer. `matched_relation` says which one fired, or is null when neither did. AN EMPTY RESULT IS A REAL ANSWER HERE, not a failure: ThreatFox is a C&C-tracking feed, not a sample database — most hashes on any malware site are in neither relation. It also expires every IOC older than six months, so a hash from an old report can legitimately return nothing today. For sample metadata (file type, size, signature, YARA) use the malwarebazaar pack, which is the same vendor and indexes every sample.
    ConnectorNo auth
  • Return a ~500-word educational explainer of M/M/c queueing theory: Little's Law, utilization, why averages mislead, how simulation relates to Erlang-C. No inputs. Use this when the user asks a conceptual 'why' or 'how does this work' question rather than asking for a number.
    ConnectorNo auth
  • Return a textbook-level description of six queueing complexity patterns beyond basic M/M/c: abandonment/reneging, priority tiers, overflow routing, skills-based routing, compound service, and server outages. Use this when the user describes real-world complexity (customers hanging up, VIP queues, specialist escalation, agent breaks, transfers) that plain M/M/c doesn't model. The tool frames each pattern conceptually and points users at ChiAha for custom modeling.
    ConnectorNo auth
  • Get code from a remote public git repository — either a specific function/class by name, a line range, or a full file. PREFERRED WORKFLOW: When search results or findings have already identified a specific function, method, or class, use symbol_name to extract just that declaration. This avoids fetching entire files and keeps context focused. Only fetch full files when you need a broad understanding of a file you haven't seen before. For supported languages (Go, Python, TypeScript, JavaScript, Java, C, C++, C#, Kotlin, Swift, Rust) the response includes a symbols list of declarations with line ranges. This is not a first-call tool — use code_analyze or code_search first to identify targets, then extract precisely what you need.
    ConnectorNo auth
  • Convert between radio frequency and wavelength. Provide either frequency in MHz or wavelength in metres, and get the full set of equivalent values: frequency in MHz and GHz, wavelength in metres, centimetres, millimetres, and feet. Essential for antenna dimensioning, waveguide selection, and quick band identification. The fundamental relationship is lambda = c / f where c is the speed of light (299 792 458 m/s).
    ConnectorNo auth
  • Calculates timing parameters for the ubiquitous NE555 / LM555 timer IC in astable (free-running oscillator) and monostable (one-shot pulse) modes. In astable mode, computes frequency, period, duty cycle, and HIGH/LOW durations from R1, R2, and C using f = 1.44 / ((R1 + 2·R2) · C). In monostable mode, computes pulse width from R and C using t = 1.1 · R · C. Standard 555 astable duty cycle is always >50%; for 50% duty cycle use a diode across R2. Useful for generating clock signals, PWM, delays, and debounce circuits. Chain from ohms_law for power calculations or resistor_color_code for component selection.
    ConnectorNo auth
  • Complete nutritional profile for a food item by FatSecret ID — all serving sizes with calories, total/saturated/trans fat, cholesterol, sodium, potassium, carbs, fiber, sugar, protein, vitamins A/C/D, calcium, iron. 2.3M+ foods (FatSecret)
    ConnectorNo auth