Skip to main content
Glama
187,022 tools. Last updated 2026-06-10 06:53

"DaVinci Resolve" matching MCP tools:

  • "What are the coordinates of [city]" / "lat lng for [place]" / "find [town] location" — resolve a place name (city, village, region) to lat/lng so the other Open-Meteo tools can use them. Free, keyless, multilingual; returns up to 100 matches ranked by population. Use before forecast / historical / air_quality / marine / flood when you only have a place name.
    Connector
  • Returns departure times for a specific WSF ferry route on a given date. Requires numeric terminal IDs — use wsdot_get_ferry_terminals to resolve terminal names to IDs. Set remainingOnly to true to show only future departures for today (useful for "next ferry" queries). For future dates, all sailings for that day are returned.
    Connector
  • Pre-flight check on markdown BEFORE writing it via update_doc / append_doc_section. Returns { ok, errors, warnings, parsed } with parsed counts per format type (imageCount, videoCount, mermaidCount, mathCount, svgCount, calloutCount, crossRefCount, mentionCount, embedCount, detailsCount, headingCount, byteSize, nodeCount, depth) plus structured DocGuardError-equivalent errors (cap breaches) and non-blocking warnings (cross-refs that don't resolve, mention ids that don't resolve, oversize sources, cap-approaching counts). NEVER writes anything; pure parse + analysis. Use when iterating on rich-format markdown to catch problems before burning a write. Cross-ref + mention resolution is gated on caller's accessible workspace set, so unresolved tokens surface in warnings.
    Connector
  • Resolve a human symbol / slug / name (e.g. 'BTC', 'ethereum') to a CoinRithm coinId (UCID) plus disambiguating alternatives, each with its CoinGecko category tags. Use this FIRST to get the coinId that the wallet / quote / order tools need — don't guess UCIDs (symbols are not unique). Paper trading only — virtual funds (50,000 mUSD). Not financial advice.
    Connector
  • Fetch complete details for a single Scrutica facility by canonical ID. Returns: operator, owner, country, power capacity (MW), GPU inventory (where disclosed), location (lat/lng), facility type, status, data_source, source_url, is_estimated flags, data quality flags, BIS Entity List exposure via the ownership chain. Resolve facility IDs first via scrutica_search.
    Connector
  • Pre-checkout review of every field about to be submitted on a formation intake: entity name, jurisdiction, package tier, EIN option, and any flagged combinations (e.g. personal name + opaque structure, DE jurisdiction + non-investor context). Returns warnings the user should resolve OR explicitly accept before paying. When to call: AFTER the user has picked names, jurisdiction, and tier — usually after `suggest_llc_entity_names` and before `start_anonymous_llc` / `create_formation_draft_session`. The preflight is a soft gate, not a hard block; it surfaces tradeoffs in plain language so the agent can talk the user through them. Input Requirements: - All fields OPTIONAL but PREFER passing everything the user has decided so far (`jurisdiction`, `package_tier`, `ein_option`, `entity_name`, alt names, `user_intent`). Empty inputs return a generic checklist. Output: `{ checklist: [{ field, status, message, severity }], warnings, ready_for_checkout, suggested_next_step }`. `ready_for_checkout` is true when no high-severity warnings remain. PREFER citing the structure-decision guides when warnings flag a structural mismatch (wrong jurisdiction for use case, package too thin for stated risk). Resolve warnings before calling `start_anonymous_llc`.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Resolve scholarly identifiers (DOI, PMID, ISBN, arXiv, ISSN, ADS, WHO IRIS) into citations (10,000+ CSL styles) and exports (BibTeX, RIS, EndNote...), plus retraction, open-access, and citation-fabrication checks. Six tools, anonymous-friendly Streamable HTTP.

  • OpenIBAN MCP — validate an IBAN's checksum + bank code and resolve the

  • Resolve a cover image URL for a book or author photo. Returns a direct HTTPS URL in the requested size (S/M/L). The Covers API always returns HTTP 200 — missing covers return a 1×1 placeholder GIF, not a 404. URLs can be embedded in markdown as ![cover](url).
    Connector
  • Fetch the complete list of countries supported by GlobKurier. Each country entry contains: 'id' (numeric country ID required by other tools), 'name' (country name), 'iso_code' (ISO 3166-1 alpha-2 or regional code), EU membership status, road transport availability, and postal code formats. ALWAYS call this tool first to resolve country IDs before calling search_products, get_product_addons, or get_search_url. Find the country by name or iso_code, then use its 'id' field value.
    Connector
  • Resolve a name or partial name to an OpenAlex ID. Returns up to 10 matches with disambiguation hints. ALWAYS use this before filtering by entity — names are ambiguous, IDs are not. Also accepts DOIs directly for quick lookup.
    Connector
  • Resolve a pharma sponsor / manufacturer name (e.g. 'Janssen Pharms', 'AstraZeneca AB') to its public ticker, so an FDA approval / trial readout / recall can be joined to 13F ownership, insider (Form 4) buys, and the confluence signal. Returns ticker, company name, exchange, and resolution method (alias|exact|fuzzy|unresolved). Returns ticker:null for private sponsors or unmatched names rather than guessing — joins must never key on a wrong ticker.
    Connector
  • Fetch a Bluesky actor's public profile by handle (e.g. "bsky.app") or DID (e.g. "did:plc:z72i7hdynmk6r22z27h6tvur"). Returns displayName, handle, DID, bio, follower/following/post counts, avatar URL, moderation labels, and pinned post AT-URI. Use this as the first step to resolve a handle to a DID before calling tools that require a DID or AT-URI. Handles and DIDs are interchangeable as input.
    Connector
  • Resolve a claim's outcome. By default auto-grades an `auto` claim by evaluating its verifiable_condition against SEC fundamentals (confirmed/refuted), or marks it `needs_review` when it can't be resolved deterministically (judgment, antecedent, or missing data). To record a human/agent judgment instead, pass `manual_status` (+ optional score/reason). Idempotent — re-scoring the same resolution is a no-op. Tier: sp500+ (sample rejected).
    Connector
  • Resolve a structured Apier compliance error code into a Norwegian-bokmål Explanation envelope sourced from the Apier Compliance Explainer (PR-049). The response carries a one-line summary, a 1–3 sentence why, an ordered list of fix_steps, an optional Apier / Altinn / Skatteetaten / Brønnøysund relevant documentation link, an optional Lovdata-style legal_basis citation when the error maps to a concrete regulatory provision, and an optional handover block (who / where / what / why) for errors a human must resolve (e.g. AUTH_INSUFFICIENT_ROLE, AUTH_NO_DELEGATION, SCOPE_MISSING). Errors agents can resolve themselves (VALIDATION_FAILED, RATE_LIMIT_EXCEEDED, NOT_FOUND, IDEMPOTENCY_KEY_MISMATCH, IDEMPOTENCY_IN_PROGRESS, UPSTREAM_UNAVAILABLE) ship `handover: null`. The full catalogue of supported error codes mirrors `EXPLAINER_ERROR_CODES` (33 codes today across auth, validation, scope, upstream, idempotency, action-execute, government, and reliability domains); pass any code an Apier endpoint returned in an error envelope. The optional `context` object carries placeholder values (org_number, role, scope, field, upstream_system) that the explainer interpolates into the bokmål text — missing values fall back to a Norwegian 'ukjent <noun>' rather than leaking placeholder syntax. Required scope: `read:rulebook`.
    Connector
  • All 30 NBA teams: ID, name, city, abbreviation, conference, division. Use as a directory to resolve a team name into the numeric team_id required by other balldontlie tools.
    Connector
  • Resolve a place name to ranked coordinate matches with country, region, elevation, timezone, and population. Required prerequisite for name-based queries — all weather tools take latitude/longitude, not place names. Returns up to 10 matches ranked by population/relevance; use country or admin1 to disambiguate when multiple cities share a name.
    Connector
  • Resolve an airport or weather reporting station by ICAO identifier, or discover stations within a bounding box or US state. Returns all identifier variants (ICAO/IATA/FAA), coordinates, elevation, and available data types (METAR, TAF, SYNOP, etc.). Station IDs must be 4-letter ICAO format (e.g., KSEA, KJFK). At least one of station_ids, bbox, or state is required.
    Connector
  • USE THIS TOOL WHEN you have free text (a memo, an email, a clause) and want every OSCOLA-style citation it contains extracted and classified. Identifies: neutral citations ([2024] UKSC 12), law reports ([2024] 1 WLR 100), legislation sections (s.47 Companies Act 2006), SIs (SI 2018/1234), retained EU law (Regulation (EU) 2016/679). Parsing is pure regex by default. Ambiguous citations (e.g. bare [2024] EWHC without division) can OPTIONALLY be disambiguated by setting disambiguate=True, which asks the CONNECTED CLIENT's own model (not this server) to resolve the division via MCP sampling — off by default. Citations resolve to TNA / legislation.gov.uk URLs when possible. AFTER calling, pass each citation through citations_resolve to verify it points at a real document before quoting or formatting it — the parser recognises the SHAPE of a citation but does not confirm the document exists.
    Connector
  • Wholesale-delete a recording (test set + its cases + mocks + mapping). `branch_id` is REQUIRED — the delete lays a tombstone overlay on the branch (mergeable). Direct deletes from main via MCP are blocked. Returns { deleted: true } on success, 404 when the (app_id, test_set_id) tuple doesn't resolve to a recording.
    Connector
  • List the Meta ad accounts connected to this Adbloop user, with the Page NAME + Instagram username + pixel each account uses. Use this to resolve a spoken account/page name to IDs.
    Connector
  • Get the full text of a specific legal provision by exact citation (e.g. '§ 823 BGB', 'Art. 6 DSGVO', '§ 280 Abs. 1 BGB'). Citation order is flexible — '§ 9 DSGVO', 'DSGVO Art. 9', 'Artikel 9 DSGVO' all resolve correctly.
    Connector