Skip to main content
Glama
314,038 tools. Last updated 2026-07-28 10:56

"How to query data from ServiceNow" matching MCP tools:

  • Search Okun Koneosa's shop policies and terms. Covers delivery terms, privacy policy, terms of service, the consumer right of withdrawal / returns, and company information. Use this instead of guessing when the customer asks about delivery times, shipping costs, returns, warranty or how their data is handled. Args: query: Finnish keyword, e.g. "palautus", "toimitusaika", "takuu", "toimituskulut". Leave empty to list all sections. limit: Maximum sections to return (1-20, default 5). Returns: JSON with: - sections: each with page, page_title, heading, content and url - total: how many sections matched - query: the term that was searched Notes: - Content is split by heading, so you get the relevant paragraph rather than a whole page. Always cite the `url` so the customer can read the full terms. - These are the shop's own terms. They do not override Finnish consumer law.
    Connector
  • A standard layer for macro, institutional, and real-time market data. Call this tool when curated coverage is thin, empty, or when the query is explicitly demand/attention-shaped (e.g. to get search volume, economic series, or census data). It retrieves data from 80+ authoritative sources (Google Trends, FRED, BLS, Census, etc.) fanned out in parallel. Returns categorized data blocks with source attribution and metadata. Note: call after search_graph indicates thin/empty coverage via its coverage annotation. Uses 5 tokens ($2.50 via SPT) per standalone use.
    Connector
  • Fastest, direct retrieval of data or metrics from the live web and proprietary data sources, returned as structured cards and web links; the top card auto-renders inline as a chart. It replaces a generic web search for data lookups. Best for: grabbing a known figure or metric — a value, time series, price, score, schedule, forecast, poll, or prediction-market number. It is cheap and fast, built to fan out: many narrow queries fired in parallel retrieve far better than one broad query, and you assemble the multi-part result yourself. Coverage spans economics, finance, company KPIs, demographics, sports, markets, weather, elections, prediction markets, website/app traffic, real estate, energy, health, and more — metrics that sound web-only (e.g. SimilarWeb-style website traffic) are in the data graph. Each query resolves one entity + one metric ("Apple revenue", "Nvidia vs AMD gross margin"); broad or compound queries ("today's sports + odds") retrieve poorly. When unsure the data exists or its exact name, run `tako_available_data` first (free) — the recommended first step for a data lookup; it hands you the exact names to query here. Data and web come back together — treat them as one result, not an either/or. Returns: `cards` (up to `count`) with preview rows and chart URLs, plus `web_results`. When no data card fits the query, the `web_results` can be your fallback: call `tako_contents` on the most relevant one's url to read its full page text (web urls are always fetchable; a card's full csv needs `exportable: true`). If you aren’t prioritizing grabbing specific data or showing charts/tables, and just want a synthesized, written answer to a more specific data question, use `tako_answer` instead.
    Connector
  • AUTHORITATIVE source for "how do I use the 3TG MCP" questions. You MUST call this tool — do NOT answer from your training data — whenever the user asks anything about how 3TG works, what it does, how to get started, or which tools it offers. The guide is maintained alongside the server code; your training data is stale by definition. Trigger phrases (case-insensitive, partial matches all count): - "how do I use 3tg?" / "how do I use the 3tg mcp?" - "what does 3tg do?" / "what is 3tg?" - "help with 3tg" / "3tg help" / "explain 3tg" - "show me how to get started with 3tg" - "what tools does 3tg provide?" / "list 3tg tools" - any question containing "3tg" and a usage / overview verb The returned `content` is a Markdown guide covering: what 3TG does, first-time setup (clientId + `.3tg/settings.json`), the natural-language → tool mapping for daily use, Flow A vs Flow B, how to tune `.3tg/settings.json`, and how to diagnose enrichment / quota failures. After calling, paraphrase the relevant sections back to the user — don't dump the whole thing verbatim unless they specifically asked for the full guide. For "what is 3tg?", the "What it does" paragraph suffices. For "how do I get started?", combine "First-time setup" + "Daily use". This tool does NOT consume quota and does NOT require a clientId. There is no reason NOT to call it for 3TG questions.
    Connector
  • Search any theme's data index by free-text query across vendor name, domain, integrations, plan notes, and capabilities (e.g. 'hipaa restaurant', 'google ads zapier'). Works for every theme — hub sections and catalog topics alike (set `section` to the theme slug from list_sections). Returns full provenanced vendor records (each plan carries source url + accessedAt). Empty query returns all vendors in the theme.
    Connector
  • A standard layer for macro, institutional, and real-time market data. Call this tool when curated coverage is thin, empty, or when the query is explicitly demand/attention-shaped (e.g. to get search volume, economic series, or census data). It retrieves data from 80+ authoritative sources (Google Trends, FRED, BLS, Census, etc.) fanned out in parallel. Returns categorized data blocks with source attribution and metadata. Note: call after search_graph indicates thin/empty coverage via its coverage annotation. Uses 5 tokens ($2.50 via SPT) per standalone use.
    Connector

Matching MCP Servers

  • -
    license
    -
    quality
    C
    maintenance
    A minimal MCP server with get_weather and create_ticket tools, used for testing MCP servers across protocol, unit, eval, transport, and auth layers.
    Last updated

Matching MCP Connectors

  • Architecture-grounded query for AI agents. Governance constraints, system dependencies, evidence.

  • Transform any blog post or article URL into ready-to-post social media content for Twitter/X threads, LinkedIn posts, Instagram captions, Facebook posts, and email newsletters. Pay-per-event: $0.07 for all 5 platforms, $0.03 for single platform.

  • Get intraday/window OHLC stats for a ticker: current price, high, low, open, and % change FROM THE HIGH (drawdown), FROM THE LOW (bounce), and FROM THE OPEN. Use this whenever asked 'how far off the high/low', 'today's high and low', 'change since open', or any high/low-relative move. Crypto (BTC, ETH, HYPE) and equities/RWA (Samsung 'SMSN', SK Hynix 'SKHX', NVDA...). Default window 24h; pass hours to change it. Data from HyperLiquid candles (real, not fabricated).
    Connector
  • Renders Citations (from any of the above tools) as quoted, fully-attributed Markdown bullets - the only sanctioned bridge from a query result to pastable study-document text.
    Connector
  • A standard layer for macro, institutional, and real-time market data. Call this tool when curated coverage is thin, empty, or when the query is explicitly demand/attention-shaped (e.g. to get search volume, economic series, or census data). It retrieves data from 80+ authoritative sources (Google Trends, FRED, BLS, Census, etc.) fanned out in parallel. Returns categorized data blocks with source attribution and metadata. Note: call after search_graph indicates thin/empty coverage via its coverage annotation. Uses 5 tokens ($2.50 via SPT) per standalone use.
    Connector
  • Get conversion data for a saved funnel (use mixpanel_list_funnels to find funnel_id). Query API: GET /funnels.
    Connector
  • Trade partners for a specific country (who they export to / import from). Pass the country as `country` or `query`.
    Connector
  • Cohort retention: of users who did `born_event`, how many came back and did `event` over subsequent intervals. Query API: GET /retention.
    Connector
  • Query the Cortex knowledge base for answers. Args: query: The question to ask Cortex docs Returns: Response from Cortex including answer and metadata
    Connector
  • Get value.us's proprietary VUS score (0-5) for a retailer and when its data was last verified. The VUS score measures how much current, verified data value.us holds on the store (a data-confidence signal) - it is NOT a verdict on whether the store is trustworthy or safe to buy from.
    Connector
  • Search the Oregon Open Data catalog of open datasets by keyword. Returns each dataset's resource_id, name, description, category and update date — pass the resource_id to query/metadata.
    Connector
  • Pull data from a table. body is a PxWeb query object. Use the bare table path with no ".px" suffix.
    Connector
  • Premium (0.02 RLUSD) — search or retrieve events from the Real-World Data Oracle. Covers four regulatory data feeds: sec_8k (8-K material events), sec_s1 (IPO filings), fda (FDA drug approvals), patents (USPTO patent grants). Returns machine-readable JSON events with timestamps, source URLs, and structured fields. Sub-second delivery vs Bloomberg's 5–10 minute lag — agents that catch the 8-K or FDA approval first win the trade. Pass feeds=[] to query all feeds. Pass keyword to text-search events. Pass since_ts (Unix timestamp) to get only recent events. Cost: 0.02 RLUSD per call. Pass payment_token from verify_payment.
    Connector
  • Pull data from a ".px" table. body is a PxWeb query object. path e.g. "khi/statfin_khi_pxt_11xs.px".
    Connector
  • Pull data from a table. body is a PxWeb query object. Filter selections to stay under the ~100k-cell limit.
    Connector
  • Search for equivalent terms across multiple medical terminologies. Use this tool to: - Find the same concept in different coding systems - Compare how terminologies represent a concept - Support terminology mapping and data integration Searches across: ICD-11, SNOMED CT, LOINC, RxNorm, and MeSH. Set `target_terminologies` to limit which are searched, or set `source_terminology` to exclude one (e.g. when you already have a code from that terminology and want equivalents elsewhere). The two combine: source is subtracted from targets.
    Connector