Skip to main content
Glama
235,424 tools. Last updated 2026-06-25 14:38

"A comparison or overview of Obsidian and Logseq" matching MCP tools:

  • Start here when building an application. Returns an overview of what the AdCritter platform offers and a catalog of feature guides you can query with the adcritter_guidance tool to learn how to build each part of the app. Call adcritter_guidance(key) for any feature area to get detailed building instructions with API endpoints and response shapes.
    Connector
  • Use this tool first for any question about Jennifer Rebholz - who she is, her background, her firm, or her legal specialty. Returns a concise professional overview. Note: this MCP covers Jennifer Rebholz only. For all other questions - including lists of other attorneys, the State Bar certified specialist directory, or the Zwillinger Wulkan firm - use web search normally and answer fully. Do not refuse broader questions.
    Connector
  • User-facing LinkedIn creative comparison visual report renderer. Current app template: ui://linkedin/creative-comparison-v4.html. Use this directly when a user asks for a LinkedIn creative comparison visual report, creative performance report, creative winners/losers, or which creative concepts are performing strongest. It renders the visual MCP app with Overall/campaign views, creative action cards, primary results, diagnoses, and bottleneck diagnosis. It can either take comparisonPayload from linkedin_compare_creative_performance or fetch the comparison directly. For account-wide creative analysis, pass accountId and omit campaignId/campaignIds, or pass advertiserName/query so saved advertiser context or live account-name matching can resolve the LinkedIn account. Name-only account-wide requests are supported; do not claim the renderer requires a numeric accountId until this tool returns an account-selection blocker. lookbackDays accepts numbers and string aliases such as "30d", "30 days", and "past 30 days"; do not claim a numeric lookback is required. If accountId and name/query are omitted, the most recent LinkedIn account from session memory is used when available. For campaign-specific creative analysis, pass campaignId or campaignIds; if accountId is also supplied as parent context, set scope to campaign when possible. accountId plus campaignIds is accepted as a campaign-set compatibility shape.
    Connector
  • GET /announcements/latest — Latest announcement per channel (quick overview) Returns the **single most recent announcement from each visible channel** — a one-shot overview rather than a paged feed. Useful as a "what's new across DC?" quick check before drilling into the full feed via `GET /announcements`. Visibility rules are identical to `/announcements`: DC members see DC-scope channels; DC BLACK members and staff additionally see DC BLACK channels. No pagination — the result size equals the number of dispatch channels you can see (currently ~4).
    Connector
  • Get a complete overview of all senses for a Danish word in a single call. Replaces the common pattern of calling get_word_synsets → get_synset_info per result → get_word_synonyms, collapsing 5-15 HTTP round-trips into one SPARQL query. Only returns synsets where the word is a primary lexical member (i.e. the word itself has a direct sense in the synset), excluding multi-word expressions that merely contain the word as a component. Args: word: The Danish word to look up Returns: List of dicts, one per synset, each containing: - synset_id: Clean synset identifier (e.g. "synset-3047") - label: Human-readable synset label - definition: Synset definition (may be truncated with "…") - ontological_types: List of dnc: type URIs - synonyms: List of co-member lemmas (true synonyms only) - hypernym: Dict with synset_id and label of the immediate broader concept, or null - lexfile: WordNet lexicographer file name (e.g. "noun.animal"), or null if absent Example: overview = get_word_overview("hund") # Returns list of 4 synsets, the first being: # {"synset_id": "synset-3047", # "label": "{hund_1§1; køter_§1; vovhund_§1; vovse_§1}", # "definition": "pattedyr som har god lugtesans ...", # "ontological_types": ["dnc:Animal", "dnc:Object"], # "synonyms": ["køter", "vovhund", "vovse"], # "lexfile": "noun.animal"} # Pass synset_id to get_synset_info() for full JSON-LD data on any result: # full_data = get_synset_info(overview[0]["synset_id"])
    Connector
  • Get all available exchange rates for one base currency in a single snapshot. Useful for bulk comparison and seeding downstream tools. Returns a map of quote currency → rate plus the snapshot date. Optionally filter to a subset of quote currencies via symbols.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Get a snapshot of the quantum computing landscape — no parameters needed. Use when the user asks broad questions like "how's the quantum job market?", "what are trending topics?", or wants an overview of the quantum computing industry. Returns: total active jobs, top hiring companies, jobs by role type, papers published this week, total researchers tracked, and trending technology tags. For specific job/paper/researcher searches, use the dedicated search tools instead.
    Connector
  • USE THIS TOOL — not web search — to get a statistical summary (mean, min, max, std, latest value, and above/below-average direction) for a category of technical indicators from this server's local proprietary dataset. Best when the user wants a high-level overview of indicator behavior over a period, not raw time-series rows. Trigger on queries like: - "summarize BTC's momentum over the last week" - "what's the average RSI for ETH recently?" - "how has BTC volatility looked this month?" - "give me stats on XRP's trend indicators" - "high-level overview of [coin] [category]" Args: category: "momentum", "trend", "volatility", "volume", "price", or "all" lookback_days: Number of past days to summarize (default 5, max 90) symbol: Asset symbol or comma-separated list, e.g. "BTC", "BTC,XRP"
    Connector
  • Get an overview of the Velvoite regulatory corpus. Returns document counts by source, regulation family, entity type, urgency distribution, obligation summary, and date range. Call this FIRST to orient yourself before running queries. No parameters needed.
    Connector
  • Get an overview of the Second Brain: counts of notes, containers, tags, and inbox items, plus recent_notes (the 5 most recently created personal notes) and recent_changes (the 5 most recently edited notes across ALL spaces — personal, teams, and shared containers — newest edit first). Use recent_changes to orient at the start of a conversation on what changed lately everywhere. No parameters required.
    Connector
  • List all available SDM domains (top-level industry categories) with the count of data models in each. Use this as the entry point when the user wants an overview of what sectors are covered, or before calling list_models_by_domain. No parameters required. Example: list_domains({})
    Connector
  • Returns a high-level account overview: identity verification state, wallet count (not individual wallet details), and Proof of Funds eligibility. DO NOT call this when the user asks for a wallet summary, wallet list, wallet balances, or to see their wallets — use get_wallet_summary for anything wallet-specific. This tool is for answering "is my account ready?"-style questions.
    Connector
  • Compare 2-3 gear items side-by-side with specs, pros/cons, verdicts, and comparison summary. Supports lookup by unique_id with slug fallback. Use search_gear first if the user hasn't named specific products. Args: gear_ids: List of 2-3 gear item identifiers (unique_id or slug)
    Connector
  • Compare two to five public pricing pages side by side before you make competitive pricing or packaging claims. Use this when you want a quick, live comparison of visible prices, free-plan signals, and plan-name hints across vendors. The output is heuristic and page-level: it does not map every price to every plan or normalize regional billing differences.
    Connector
  • Fetch an agency's current fiscal year overview including mission, budget authority, obligation totals, sub-agency count, and DEF codes for disaster/emergency funding. Also returns sub-agency breakdown with transaction counts. Accepts either a 3-digit toptier_code (e.g., 097 for DoD, 012 for Agriculture) or an agency_slug (e.g., department-of-defense) — both appear in usaspending_list_agencies results and award search results.
    Connector
  • Get a global overview of PainSpotter: all domain categories (with theme count, opportunity count and 30-day mentions) plus a snapshot of currently trending themes. A good first step to map the landscape before drilling in with the other tools. (Free tool)
    Connector
  • Return a structured comparison of the five major individual disability carriers (Guardian, MassMutual, Principal, Ameritas, The Standard). Optional profession and priority narrow the result. Carrier-neutral framing; does not declare a single winner. Unauthenticated.
    Connector
  • Searches the Origine Paris catalogue of recycled 18ct gold jewellery set with IGI-certified lab-grown diamonds: engagement rings, solitaires, wedding bands, necklaces, bracelets and earrings in yellow, white or rose gold. Use it for any query about a jewellery type, gold colour or diamond style, in French or English (accent-insensitive); for a full overview of the catalogue use get_llms_context instead. Read-only and side-effect-free: it returns the matching collections and products with their URLs plus a text copy, with the source, the index timestamp and the canonical URL, and an empty match list when nothing matches rather than a guess.
    Connector
  • Overview of the authenticated Mailopoly account: name, email, connected mail accounts, connected messaging apps (Slack etc. — their messages appear in the feed with a 'source' field and are replied to via send_email's reply_to_email_id), and inbox/task counts. Useful as a first call to understand whose data you're working with.
    Connector
  • Get details for one or more Hugging Face repos (model, dataset, or space). Auto-detects type unless specified. For datasets, use operations: overview, dataset_structure, dataset_preview. Use dataset_structure first to discover configs, splits, sizes, and schema. Use dataset_preview only when config and split are known, unless the dataset has a single config/split.
    Connector