Skip to main content
Glama
730,291 tools. Updated 2026-10-31 20:15

"Weights & Biases" matching MCP tools:

  • Create or update a custom scoring profile. Profiles are sparse overrides: only specify the weights you want to change. Everything else keeps its default value. If a profile with this name already exists, it is updated with the new weights (full replacement, not merge). Weights are points, not percentages. Each weight is the number of points that signal adds to the score when it fires. They don't need to total 100. A profile with weights totalling 90 is conservative (max possible score is 90). A profile with weights totalling 130 is aggressive (multiple signals quickly push to the cap of 100). The threshold the agent sets for action matters more than the weight totals. Use show_defaults to see all 25 signals with their default weights and descriptions before creating a profile. Use check_url or check_urls with the "profile" parameter to score results with this profile. Maximum 20 profiles per account. Profile name "default" is reserved. Common profiles: - Cold email: weight parked (30), chain_incomplete (25), ssl_invalid (15) higher. Lower brand_impersonation (10). - Security bot: keep brand_impersonation high (40), increase domain_age_7 (30), redirects_5 (25). - Lead gen: weight parked (35), http_only (20), chain_incomplete (20) for dead business detection. - SEO audit: weight redirects_5 (30), chain_incomplete (30), parked (25) for link quality. See the Unphurl API documentation for all 19 use case weight examples.
    ConnectorNo auth
  • Change how often a video plays (weight 0-10, default 5; 0 removes it from rotation entirely), and optionally its title or tags. IMPORTANT ORDERING: weights only affect what actually airs when the schedule is (re)generated. A channel builds its schedule the instant it crosses the launch threshold, so weights set AFTER that are stored but do not air. Either set the weight when you import each video, or call regenerate_schedule afterwards. Weights are relative: identical weights across every video produce a uniform rotation, and the spread between them is what shapes airtime.
    ConnectorNo auth
  • Rebuild the channel's schedule now using the current weights. Call this after changing weights on a channel that is ALREADY live, otherwise the change will not air until the hourly cron. Throttled to one call per channel per 5 minutes; exceeding that returns 429 with a Retry-After header giving the seconds remaining. Requires the channel to meet launch requirements.
    Connector
    Destructive
    No auth
  • Use this when the user wants a weighted decision matrix, scored comparison, alternative ranking, or weight sensitivity analysis with explicit criteria, weights and scores. Accepts two to twenty options and one to eight criteria. Scores use a fixed zero-to-one-hundred scale; benefit means higher is better and cost means lower is better. Returns normalized weights, exact rankings and ties, pairwise break-even shares, up to four explicit weight scenarios and CSV. Does not research options, invent scores, infer preferences or predict outcomes.
    ConnectorNo auth
  • Use this when the user asks what they did in past gym workouts: exercises, sets, reps and weights ("show my last 5 workouts", "what did I do this week?"). Returns finished workouts, newest first, with their exercises, sets and `routine_name` (the routine it was started from, or null). Filter by `from` / `to` and `exercise_slugs`; defaults to the last 30 days and 20 workouts, at most 100 per call. It has only what was logged in the Reps app (sets, reps, weights, durations): no heart rate, pace, GPS or data from a watch or another app, so do not call it for those.
    ConnectorOAuth
  • Builds a custom portfolio of US listed ETFs from construction choices about the portfolio, and shows the rule it applied. Two forms. Weights (ETFIQ custom construction rule, version 2): pass weights, the user's own percent for each asset class, adding to exactly 100, for example {"us-stocks": 40, "international-stocks": 15, "us-bonds": 25, "gold": 10, "reits": 10}. The asset classes: us-stocks, us-small-stocks, international-stocks (broad, market-cap-weighted index funds only), international-dividend-stocks, international-esg-stocks, international-factor-stocks, international-ipo-stocks (each only when the user asks for that tilt), emerging-markets-stocks, reits, us-bonds (core, intermediate), us-bonds-short, us-bonds-long, us-corporate-bonds, government-bonds-short, government-bonds-intermediate, government-bonds-long, tips, high-yield-bonds, cash (Treasury bills), gold, commodities (broad), alternatives. Defaults: cheapest funds, one fund per asset class, no fee ceiling; the answer's defaults.line names the ones used. Band (version 1): pass band, include and funds, and the rule sets the weights (stocks at the band's point, international, broad market-cap-weighted funds only, 40% of stocks outside themes, themes 10% of stocks, commodities and alternatives 5% each from bonds, US bonds the rest). In each asset class or sleeve the cheapest (or largest) funds that file N-PORT (a gold trust: its 10-Q or 10-K), hold at least $100 million and have three years of prices, each fund's fee with its filing date. Weights given in words go to the weights form mapped to the ids above. Only two things have no default, and each is refused with its kind: weights that do not add to 100 (kind weights-total) and an asset class with no id here (kind unknown-class). With neither weights nor a band, the tool needs one of them; the bands by stock share are conservative: more than 15% and up to 30% stocks; moderately-conservative: more than 30% and up to 50%; moderate: more than 50% and up to 70%; moderately-aggressive: more than 70% and up to 85%; aggressive: more than 85%. The tool takes nothing about the person: an argument giving their age, income, savings, net worth, goals, time horizon, tax situation, risk tolerance, employment or family is refused (kind person), and weights and bands are the user's choices about the portfolio, not facts about someone. Whether a portfolio suits someone, or whether to buy or sell it, is not something ETFIQ answers, and the not-advice line says so. Its returns field carries the portfolio's hypothetical returns (ETFIQ custom rule, version 3: the weights reset at every month end, as the ETFIQ benchmarks are): total return, return a year, volatility and month-end drawdown over 1Y, 3Y, 5Y, 10Y and since the first month end all its funds share, a window given only where every fund has prices across it; returns.common.sentence says where the history starts and why. They are hypothetical: no window is extended, and no return is estimated beyond the ones given. compare_to_benchmark takes the answer's compare.arguments to set the portfolio beside an ETFIQ benchmark. Every response carries the not-advice line in not_advice, written to be shown with the portfolio.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Risk, diversification, fundamentals and outlook for holdings given in the conversation. Nothing is stored. ``sections`` narrows the answer; 'weights' adds the breakdown. Each line is an ``asset_id`` (as find_assets, screen_equities and the solve tools return it), else an isin, ticker or name, or a ``cash_currency`` for cash, sized by one of ``weight``, ``units`` or ``market_value``. Amounts and units mix freely; weights cannot mix with either. A name that matches nothing close to it is listed as not included rather than replaced by another company, and a name matched to a differently spelt instrument is listed for checking.
    ConnectorOAuth
  • Delete a custom scoring profile. This is permanent. Any future check requests using this profile name will fall back to default weights. Use list_profiles to see your current profiles before deleting.
    Connector
    Destructive
    No auth
  • Compute portfolio-level statistics for a weighted basket of tickers. Given a {ticker: weight} mapping, fetches each ticker's daily history over range and returns the portfolio-level (not per-ticker) volatility, sharpe, max_drawdown and total_return of the weighted basket. weights need NOT sum to 1 (normalized internally). Tickers that cannot be fetched are dropped, a note is added to warnings, and the remaining weights are renormalized. risk_free_rate is an annual rate used only by Sharpe. Returns the standard envelope; values holds range, the normalized weights used, and the stats dict. (paid: $0.0100/call)
    ConnectorNo auth
  • List NIST SP 800-171 Rev 2 requirements with their DoD Assessment Methodology (SPRS) weights, optionally filtered by control family name or by point weight (5, 3, or 1). Call this to enumerate the 110 CMMC Level 2 controls, to find all 5-point (highest-impact) requirements, or to see everything in one family such as Access Control. Returns identifiers and weights only - use lookup_control for one requirement's full text, or pass verbose to include every requirement's text at roughly twenty times the size.
    ConnectorNo auth
  • Every HTTP endpoint with its auth requirement, body shape and worked examples, plus the reputation weights and citation semantics as data. Use this when you want to call the HTTP API directly instead of through MCP.
    ConnectorNo auth
  • Use before interpreting a performance or signal claim, especially when a user asks for assumptions, limitations or possible bias. Explains how the engine decides, what the published numbers do and do not claim, and the known biases in the record. Read this before quoting any statistic from the other tools.
    ConnectorNo auth
  • Turn a {ticker: score} mapping into long-only portfolio weights. Selects names and assigns non-negative weights that sum to 1.0 using the chosen method: top_n_weighted (weight by clipped score), equal_weight, risk_parity (inverse-volatility), concentrated_vol (highest-vol from a top-score pool), or sharpe_optimized (max-Sharpe long-only). The last three fetch daily history over range (5d,1mo,3mo,6mo,1y,2y,5y,max) and convert it to returns; tickers that fail to fetch are dropped with a warning. Returns the standard envelope; values holds method, top_n, a weights map, and n_holdings. (paid: $0.0100/call)
    ConnectorNo auth
  • Scores up to 200 entities in one round-trip — built for agents evaluating many supply sources during campaign setup. Per-item parse failures (e.g. a bad domain) are returned inline, with one exception: a malformed `app_bundle` id rejects the whole batch with 400. An optional `weights` object re-weights every entity in the call. Cost: - Each entity costs one rate-limit unit (the first is the request itself). A batch larger than the remaining budget is refused whole with 429 and charges nothing beyond that first unit, so the effective maximum per call is min(200, remaining + 1): anonymous 10/min, free 50/day, supporter 500/day, pro 5,000/day, enterprise unlimited.
    ConnectorNo auth
  • Upsert a named watchlist with a list of tickers. Replace semantics — the full ticker list is the source of truth for that name. Use this for both creation AND modification (delete + recreate is not required for edits). 500-ticker cap per list. Names are case-insensitive uniqueness. Optional `weights` (ticker → relative number) marks a list the user HOLDS rather than merely follows; omit it entirely for an ordinary watchlist, and omit it on an edit to leave existing weights untouched.
    ConnectorNo auth
  • Extract structured contract metadata (contracting parties, effective and termination dates, total contract value, payment terms, key deliverables, security clearances, and governing law) from unstructured B2B contracts, Statements of Work (SOWs), or RFPs into normalized JSON. This is a read-only, stateless, non-destructive extraction call (requires X-RapidAPI-Key; accepts 50 to 100,000 characters in `raw_text`, and `document_type_hint` optionally biases extraction rules toward federal RFP, MSA, SOW, or NDA conventions). Use this tool when you need general commercial or header metadata from a contract; use `extract_pricing_schedule` instead for line-by-line CLIN/rate-card tables, `audit_contract_risks` for toxic clause redlining, or `generate_compliance_matrix` for Section C/L/M requirement shredding.
    ConnectorNo auth
  • Extract structured contract metadata (contracting parties, effective and termination dates, total contract value, payment terms, key deliverables, security clearances, and governing law) from unstructured B2B contracts, Statements of Work (SOWs), or RFPs into normalized JSON. This is a read-only, stateless, non-destructive extraction call (requires X-RapidAPI-Key; accepts 50 to 100,000 characters in `raw_text`, and `document_type_hint` optionally biases extraction rules toward federal RFP, MSA, SOW, or NDA conventions). Use this tool when you need general commercial or header metadata from a contract; use `extract_pricing_schedule` instead for line-by-line CLIN/rate-card tables, `audit_contract_risks` for toxic clause redlining, or `generate_compliance_matrix` for Section C/L/M requirement shredding.
    ConnectorNo auth
  • Get the full SYX methodology — how the index is constructed, which onchain components are included, how weights are calculated, the measurement windows, and the exclusion rules. Use this when the user asks "how is SYX calculated" or "what does SYX measure" or "what protocols does SYX include".
    ConnectorNo auth
  • Get the full transparency methodology — how we collect, assess, extract, sign, and verify political data. Includes quality assessment algorithm (signals + weights), trust levels, data sources, cron schedule, and what we can and cannot prove. Open and auditable.
    ConnectorNo auth
  • List all custom scoring profiles on this account. Returns profile names and their custom weight overrides. Profiles are named weight sets that change how Unphurl scores URLs. Different use cases need different scoring. A cold email agent cares about dead domains. A security bot cares about phishing. Profiles let one account serve multiple use cases. Profiles only override specific weights. Any signal not specified in a profile uses the default weight. Use show_defaults to see all 25 signals and their default weights.
    ConnectorNo auth
  • Returns the active, versioned default weights used to combine an entity's trust-score components, plus the list of spec components that are not yet evaluated. Pass a custom `weights` object to `sigil_score_batch` to re-weight without changing the defaults.
    ConnectorNo auth