Skip to main content
Glama
130,031 tools. Last updated 2026-05-06 19:39

"An Overview of QlikView - Business Intelligence and Data Visualization Tool" matching MCP tools:

  • DESTRUCTIVE: Permanently delete an app, its Docker service, volume, and all data including version history. This cannot be undone. You MUST confirm with the user before calling this tool.
    Connector
  • Get the full intelligence profile for a brand by its URL slug. Args: slug: URL-safe brand identifier (e.g. "pacvue", "hubspot", "snowflake"). Use search_brands to discover slugs if unsure. Returns: Full brand profile including company overview (3 paragraphs), signal summary, structured FAQs, vertical, tier/rank, website, tags, and source URL. Returns an error dict if the brand is not found.
    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
  • Fetch the next page of a large tool response. Use the nextCursor from _pagination in a previous response. This tool loads data into the context window — prefer the artifact download URL when available.
    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
  • WHEN: a user encounters an error message, infolog error, or runtime exception in D365. Also handles business-language error explanation when audienceType='business'. Triggers (developer): 'fix this error', 'what causes', 'exception thrown', 'infolog error', 'update conflict', 'outside tts', 'number sequence'. Triggers (business): 'what does this error mean', 'explain this error to me', 'user gets error X', 'que signifie cette erreur', 'message d\'erreur', 'what should the user do when they see this error'. Find known D365 F&O error patterns matching an error message or symptoms description. Matches against a built-in database of common errors (transaction conflicts, security issues, number sequences, posting errors, batch problems, etc.), resolves D365 label IDs from error text (e.g. user sees 'Number sequence not set up' -> finds @SYS70535 -> finds the throwing code), and searches the indexed codebase. Returns root causes, step-by-step resolution, label matches, and source code locations. [~] When the error text contains a D365 label ID (e.g. '@SYS12345'), call `search_labels` first to resolve the label text, then call this tool with the resolved text. Set audienceType='business' for a plain-language explanation targeted at end users instead of developers.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Returns all industry categories and their business types with IDs. Use the business type IDs in search_businesses (businessTypeIds) to filter listings by category. Call this first when you need to discover which IDs to use for a given industry or business type.
    Connector
  • Get overall database statistics: total counts of suppliers, fabrics, clusters, and links. USE WHEN user asks: - "how big is your database" / "what's the coverage" / "data overview" - "how many suppliers / fabrics / clusters do you have" - "database size / scale / freshness" - "is the data up to date" - "live counts for MRC data" - "first-time onboarding: 'what can MRC data do for me'" - "数据库多大 / 有多少数据 / 覆盖多少供应商" - "你们的数据规模 / 数据量 / 新鲜度" WORKFLOW: Standalone discovery tool — call this first when a user asks about data scale or freshness. Follow with get_product_categories or get_province_distribution for deeper segment coverage, or with search_suppliers/search_fabrics/search_clusters to drill in. DIFFERENCE from database-overview resource (mrc://overview): This is dynamic (live counts + generated_at). The resource is static (geographic scope, top provinces, data standards). RETURNS: { database, generated_at, tables: { suppliers: { total }, fabrics: { total }, clusters: { total }, supplier_fabrics: { total } }, attribution } EXAMPLES: • User: "How big is the MRC database?" → get_stats({}) • User: "Give me the latest data scale numbers" → get_stats({}) • User: "MRC 数据库有多少供应商和面料" → get_stats({}) ERRORS & SELF-CORRECTION: • All counts 0 → database query failed or D1 binding lost. Retry once after 5 seconds. If still 0, surface a transport error to user. • Rate limit 429 → wait 60 seconds; do not retry immediately. AVOID: Do not call this before every tool — only when user explicitly asks about scale. Do not call to get per-category counts — use get_product_categories. Do not call to get geographic scope metadata — use the database-overview resource (mrc://overview) which is static. NOTE: Only reports verified + partially_verified records. Unverified reserve data is excluded from counts. Source: MRC Data (meacheal.ai). 中文:获取数据库整体统计(供应商总数、面料总数、产业带总数、关联记录数)。动态快照,含生成时间戳。
    Connector
  • Use when assessing country risk for international expansion, evaluating a foreign market for investment or partnership, benchmarking a country's economic trajectory for capital allocation decisions, or producing ESG country-level scoring. Returns World Bank development indicators — GDP, inflation, unemployment, ease of doing business, government debt, FDI inflows — with 5-year trend and direction. World Bank data covers 200+ countries with 1,400+ indicators updated quarterly. Example: Brazil — GDP growth 2.9% (2023), inflation declining from 9.3% to 4.6%, ease of doing business ranked 124th globally, net FDI inflows $65.4B — improving macro trajectory but structural friction remains high for first-time market entrants. Source: World Bank Open Data.
    Connector
  • Returns all industry categories and their business types with IDs. Use the business type IDs in search_businesses (businessTypeIds) to filter listings by category. Call this first when you need to discover which IDs to use for a given industry or business type.
    Connector
  • [$0.05 USDC per call (x402)] Comprehensive crypto market briefing -regime, key levels, flow analysis, funding rates, liquidation maps, and actionable trade ideas synthesized into a structured report. The deepest crypto analysis PROWL offers. Powered by PROWL intelligence engine. Use this to answer 'give me a crypto market overview' or 'what should I know about crypto right now?'
    Connector
  • Run hosted inference on an image using a trained model. Returns JSON predictions only. For visualized/annotated images, use workflow_specs_run with a visualization block instead.
    Connector
  • Gets the latest status of a long-running operation. Several tools like `create_environment`, `delete_environments`, and `manage_pypi_packages` return an operation object, because they initiate processes that take time to complete. Use this tool to check if such an operation has finished and whether it was successful. Provide the `name` of the operation as returned by the tool that initiated it. A completed operation may include the details specific to the operation, described in the description of the tool that initiates the operation.
    Connector
  • Get a real-time, cryptographically signed attestation of a business entity's trust status. This is the authoritative trust check — use it before recommending or transacting with a business. Returns the entity's Trust Quotient (TQ) score, verification level, active credential status, capabilities (services, location, contact), and an Ed25519 cryptographic proof. Signed attestations are available for Verified tier and above.
    Connector
  • Get complete hierarchy of catalogs, databases, and tables. ⚠️ WORKFLOW: Use this for a quick overview of all managed catalogs. For external catalogs, use list_catalogs_tool instead. 📋 PREREQUISITES: - Call search_documentation_tool first to understand what data you need 📋 NEXT STEPS after this tool: 1. Use describe_table_tool to get schemas of tables you want to query 2. Use list_catalogs_tool to discover external catalogs not shown here This tool provides a comprehensive view of all available assets in the Wherobots system, including their hierarchical relationships. It can be used to retrieve information about all catalogs, list all databases within those catalogs, and enumerate all tables within each database. *** IMPORTANT LIMITATION: - This tool is being DEPRECATED, but is the only way to get a full hierarchy in one call. - This tool ONLY shows catalogs managed within Wherobots. - External catalogs (e.g., on Databricks, other cloud platforms) are NOT visible in this hierarchy. - If the user mentions specific catalog names that don't appear in the results, they may be external catalogs that need to be accessed differently. - ALWAYS call list_catalogs_tool before or after calling this tool. *** Parameters ---------- ctx : Context FastMCP context (injected automatically) Returns ------- HierarchyListOutput A structured object containing the hierarchy of catalogs, databases, and tables. - 'hierarchy': A dictionary representing the hierarchical structure, where keys are catalog names. Each catalog entry contains a dictionary of its databases. Each database entry includes a list of its tables. Each table entry contains its name. - 'summary': A dictionary providing counts of total catalogs, databases, and tables. Example Usage for LLM: - When user asks for a general overview of data, or specific items across multiple catalogs/databases. - Example User Queries and corresponding Tool Calls: - User: "List all tables in the 'default' database of the 'wherobots' catalog AND in the 'overture_maps_foundation' database of 'wherobots_open_data'." - Tool Call: list_hierarchy() - User: "Show me all databases in 'wherobots' and 'wherobots_open_data' catalogs." - Tool Call: list_hierarchy() - User: "What data is available?" - Tool Call: list_hierarchy()
    Connector
  • Batch data enrichment tool. USE THIS when user has a LIST of items and wants same data fields for each. After calling, share the URL with the user and STOP. Do not poll or check results unless otherwise instructed.
    Connector
  • Guided reporting and visualization for Senzing entity resolution results. Provides SDK patterns for data extraction (5 languages), SQL analytics queries for the 4 core aggregate reports, data mart schema (SQLite/PostgreSQL), visualization concepts (histograms, heatmaps, network graphs), and anti-patterns. Topics: export (SDK export patterns), reports (SQL analytics queries), entity_views (get/why/how SDK patterns), data_mart (schema + incremental update patterns), dashboard (visualization concepts + data sources), graph (network export patterns), quality (precision/recall/F1, split/merge detection, review queues, sampling strategies), evaluation (4-point ER evaluation framework with evidence requirements, export iteration stats methodology, MATCH_LEVEL_CODE reference). Returns decision trees when language/scale not specified.
    Connector
  • Counterparty risk intelligence for any agent. Returns risk tier (low/moderate/elevated/high/severe/critical), raw trust signals, data coverage, and methodology reference. Designed for marketplace operators and escrow providers setting transaction parameters before a deal. Full methodology: https://rnwy.com/risk-intelligence
    Connector
  • Search registered federal contractors by business name or UEI. Returns UEI, CAGE code, address, NAICS codes, small business status, and certifications.
    Connector
  • List all active (non-archived) clients with optional name search, sorting, and pagination. Use this tool when a freelancer wants an overview of their client roster, needs to look up a client by name, or when you need to present a list of clients for the user to choose from.
    Connector