Skip to main content
Glama
306,540 tools. Last updated 2026-07-25 12:21

"A system for monitoring and operating terminals" matching MCP tools:

  • Fetch a consolidated metrics snapshot for a single stock by ticker: identity (company, exchange, currency, sector, industry, country, ISIN), latest daily price (OHLCV), latest valuation (market cap, P/E, dividend yield, annual dividend per share), the most recent reported financials (revenue, gross/operating income, EBITDA, net income, diluted EPS, free & operating cash flow, total debt, cash, total assets, equity) and a short company description. Use the exact ticker as listed on Bullrun - the native local-exchange symbol (e.g. AAPL, BMW, ABBN, NESN, or a numeric code like 005930), NOT Yahoo-style country suffixes like BMW.DE or ABBN.SW. If a ticker returns no data, use screen_stocks (by sector/country) to find the exact symbol. Read-only.
    Connector
  • Get a company's income statement, balance sheet, or cash-flow statement for a given fiscal year and period, sourced from SEC Company Facts (structured XBRL). Returns the standard line items (e.g. revenue, net income, total assets, operating cash flow) with the latest-restated value for the period. Company-specific dimensional facts (e.g. product-segment revenue) are not included — use GetRevenueBreakdown for segment/geographic revenue, and GetFinancialFact or CompareFinancialFact for one line item across periods or across companies.
    Connector
  • Validate whether a component will work within your operating conditions. Compares your design parameters against the datasheet's absolute maximum ratings and recommended operating conditions. Returns PASS/FAIL/WARNING per parameter with margin percentages. Parameter mapping by component type: - Buck/boost converters: input_voltage, output_voltage, output_current, ambient_temp - MOSFETs: supply_voltage=VDS, output_current=ID (drain current), ambient_temp - LDOs: input_voltage, output_voltage, output_current, ambient_temp - Logic ICs: supply_voltage=VCC, ambient_temp Result semantics (per-parameter 'result' field): - PASS: comfortable margin. For a recommended-operating RANGE, any value inside the range (including the exact edges) is PASS. For an absolute-MAX rating, PASS means more than 10% below the limit. - WARNING: for absolute-max ratings only, the user value is within 10% of the limit (but not over) — part will work but with thin margin for part-to-part variation, temperature drift, and transients. Consider derating. - FAIL: user value is outside the allowed range / exceeds the limit — part is out of spec and will be stressed or damaged. - INSUFFICIENT_DATA: the check could not be completed safely — most commonly an ambient_temp input that could not be translated to a junction-temperature check (see the temperature note below). INSUFFICIENT_DATA never counts as a PASS: it pulls the overall verdict down to at-least-WARNING. Each check also reports 'limit_type' (max / min / range / fixed) so you can see whether it was judged against an operating range, an absolute-max rating, or a fixed-output setpoint. Temperature honesty: - ambient_temp is NOT silently treated as a junction temperature. The stored operating-temperature limit is junction-suspect, so a bare ambient input is never reported as a clean PASS on thermal grounds. If you also supply input_voltage, output_voltage and output_current AND a thermal-resistance (RthJA) value is available, the tool estimates Tj = Ta + Pd·RthJA (Pd ≈ (Vin-Vout)·Iout, a documented approximation) and checks the junction estimate — reported as 'temperature (junction est.)' with the assumptions in the note. Otherwise the temperature check returns INSUFFICIENT_DATA asking you to pull RthJA via read_datasheet. The 'temperature_basis' field (junction / ambient / unknown) tells you which basis was used. Behavior: - Two-tier validation. For parameters in our structured database (Vin, Iout, operating temp, etc.), returns instantly and free of LLM cost. For parameters only found in the datasheet text, falls back to an LLM read of the absolute-max and recommended-operating-conditions sections. The 'validation_method' field in the response tells you which path was used. - If the part hasn't been extracted yet and the LLM fallback is needed, this call triggers extraction (30s-2min). Returns status='extracting' if so — poll check_extraction_status and retry. When NOT to use: - You need power dissipation or junction-temperature rise — this tool only checks nameplate limits. Pull RthJA from read_datasheet and calculate yourself. - You need SOA (safe-operating-area) curve checks for MOSFETs — use analyze_image on the SOA graph. - You're checking a passive or mechanical part with no abs-max table — there's nothing for this tool to compare against. Example: check_design_fit('TPS54302', input_voltage=24, output_current=2.5, ambient_temp=70)
    Connector
  • List all television stations available for TV search with their market, network, monitoring start date, and monitoring end date. Stations with an end date within the last 24 hours are flagged as active; stations with earlier end dates are discontinued. Use before querying to verify a station was active during the target time period, or to discover valid station IDs for the stations parameter in other TV tools. Most station monitoring ended October 2024 when the Internet Archive TV feed stopped updating.
    Connector
  • 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).
    Connector
  • List supported Linux operating systems and their corresponding versions for use with the `linux_audit` tool. ## What this tool does Returns an array of supported OS/version pairs, each in the form: {"os":"name", "versions":["version or codename"]} This allows the LLM and the user to know exactly which inputs are valid for the `linux_audit` tool. ## When to use this tool Use this tool when: - the user does not know which OS names or versions are supported - the user provides unclear or ambiguous OS information - you need to validate `os`/`version` before performing a Linux audit This tool should typically be called **before `linux_audit`** whenever parameters are uncertain. ## Inputs This tool does not require any input. ## Outputs Returns an array of objects: - **os**: supported Linux distribution identifier - **versions**: corresponding list of supported release or codename Example: [ {"os": "ubuntu", "versions": ["noble","focal"]}, {"os": "debian", "versions": ["bookworm","sid"]}, {"os": "redhat", "version": ["redhat-9.0"]} ] ## LLM usage guidelines - Use this tool to validate or suggest correct OS/version combinations before calling `linux_audit`. - If the user provides invalid or misspelled OS names, retrieve the official list here and ask them to select one. - Do not guess operating system identifiers-always rely on this tool to confirm correctness.
    Connector

Matching MCP Servers

  • A
    license
    C
    quality
    D
    maintenance
    Enables interaction with Google Cloud services including billing cost analysis, log querying, and metrics monitoring through natural language commands. Provides comprehensive tools for managing GCP resources, analyzing costs, detecting anomalies, and retrieving operational insights.
    Last updated
    40
    1
    Apache 2.0
  • A
    license
    -
    quality
    A
    maintenance
    Governs and automates network monitoring across SolarWinds Orion and Paessler PRTG platforms with a unified MCP server, enabling querying, alert management, and governed writes with audit logging.
    Last updated
    MIT

Matching MCP Connectors

  • Client-website monitoring for agencies: uptime, incidents, SSL/domain expiry, server metrics.

  • Site & competitor monitoring: snapshots, evidence-backed diffs, briefs, price checks, mentions.

  • Use this read-only monitoring tool to retrieve the latest meaningful DeltaSignal daily change snapshot. It highlights tracked crypto filing deltas, newly discovered crypto issuers, source dates, computed timestamps, classification summary, and change statistics. Parameters: none; call it exactly as-is when the user asks what changed today or needs a monitoring summary. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write notifications, files, accounts, or wallet state. Use it for daily monitoring and freshness narratives; use readiness for service health and issuer-specific tools for detailed research on any ticker it mentions.
    Connector
  • Use this read-only monitoring tool to retrieve the latest meaningful DeltaSignal daily change snapshot. It highlights tracked crypto filing deltas, newly discovered crypto issuers, source dates, computed timestamps, classification summary, and change statistics. Parameters: none; call it exactly as-is when the user asks what changed today or needs a monitoring summary. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write notifications, files, accounts, or wallet state. Use it for daily monitoring and freshness narratives; use readiness for service health and issuer-specific tools for detailed research on any ticker it mentions.
    Connector
  • Invert a US stock's current price into the bet it implies: the operating-income growth rate, how many years it must be sustained, and (where the route holds one as an input) the terminal operating margin assumption, versus what the company has actually delivered (from SEC EDGAR filings, reverse-DCF). boothcheck does not return a Boothcheck house fair value, price target, or buy/sell rating — it shows what the price assumes so the user can judge the bet. Covers about 2,000 US tickers.
    Connector
  • Return detailed information for a single port — identity, country, UN/LOCODE, classification, coordinates, maritime area, and the list of terminals (name, operating company, coordinates, address, website). Look up the port by its Datalastic uuid or its UN/LOCODE (exactly one). To search for a port by name or location, or when you don't have an exact identifier, use find_ports first.
    Connector
  • Assign a lead to a workspace member by user id, or pass assignedTo=null to unassign. Use search_leads to find the lead id and get_workspace_info to confirm the operating workspace. The result echoes the operating workspace.
    Connector
  • One-call comparative 'cost of operating a business here' read for a US state (with optional metro context). Joins three independent public sources, each a real operating-cost dimension expressed RELATIVE to the US national average (national = 1.00) so the result is a readable, comparable index: LABOR cost from BLS QCEW private-sector average annual pay across all industries (keyless), ENERGY cost from EIA retail electricity price for the commercial and industrial sectors (state vs national), and local CONTEXT from US Census ACS median household income, per-capita income, and median gross rent (needs a Census key; degrades gracefully). Returns a headline relative-cost banding (LOW / MODERATE / HIGH cost vs national) from a labor-weighted composite of the labor and energy indices, with each dimension's numbers and its own banding shown. Labor and energy are state-level; a supplied metro refines the context leg and label only. A source that fails is noted, not fatal. Informational, not a guarantee.
    Connector
  • Get Google organic search results for SEO rank tracking. Returns up to 100 results per request with position, title, URL, and snippet. Ideal for monitoring keyword rankings and SERP analysis.
    Connector
  • Returns real-time AIS positions, speed, heading, ETA, and dock status for all active WSF vessels. Use for "where is the ferry now?", vessel tracking, or checking if a vessel is in service. Position data may lag by 30–60 seconds. Many fields are null for vessels not currently operating.
    Connector
  • Start here: platform overview, the proposal/approval operating model, auth rules, common flows, and agent etiquette. Static content — requires no scopes.
    Connector
  • Vet a US motor carrier (trucking company) for a freight-brokerage 'is this safe and legit to broker a load to?' decision, in one call. Give a USDOT number, MC number, or carrier name. Joins FMCSA safety data (operating authority, insurance on file, BASIC safety scores, crash and out-of-service history vs the national average, safety rating) with sanctions screening (OFAC/UN/EU/BIS on the carrier's legal name), federal-court litigation history (CourtListener), and USAspending federal awards. Returns a GO / CAUTION / NO-GO verdict with the reasons, plus all the underlying fields. NO-GO is triggered by a sanctions match or lack of active operating authority; CAUTION by BASIC alerts, fatal crashes, missing liability insurance, high out-of-service rates, or litigation. This is an analytical aid, not a substitute for your own carrier-onboarding checks.
    Connector
  • Find alternative / cross-reference components for a given electronic or electromechanical part number (connectors, terminals, seals). NOTE: the substitutes dataset is under construction — this tool currently returns no matches but records demand.
    Connector
  • Mandatory initialization step for any session against the Blockscout MCP server. Returns server reference data plus the `blockscout-analysis` skill pointer and URI resolution rule. MANDATORY FOR AI AGENTS: Call this tool first in every session. The returned payload identifies where the operating rules and analysis framework live and how to read referenced skill files before executing further tool calls.
    Connector
  • Mandatory initialization step for any session against the Blockscout MCP server. Returns server reference data plus the `blockscout-analysis` skill pointer and URI resolution rule. MANDATORY FOR AI AGENTS: Call this tool first in every session. The returned payload identifies where the operating rules and analysis framework live and how to read referenced skill files before executing further tool calls.
    Connector
  • Returns reference data for a supported MLP ticker — current cash distribution per unit, distribution growth CAGR, default return-of-capital percentage, distribution coverage ratio, K-1 entity count, operating-state count, and last-verified date. Use when: User wants to look up baseline characteristics of an MLP before modeling — e.g., comparing distribution coverage across partnerships, checking how many K-1 entities a holding generates for tax-prep complexity, or seeing the operating-state count for state-tax filing-burden estimation. Don't use for: Tax computation. Use mlp_projection (long-horizon modeling), mlp_estate_planning (estate analysis), mlp_sell_vs_hold (break-even sell price), or k1_basis_compute / k1_basis_multi_year (computing basis from actual K-1 data). Note: This tool returns reference data only — no IRC citations apply, no methodology disclosure attached. For computation, use the modeling tools above. Maintained by Lucas Andersen, MS Finance.
    Connector