Skip to main content
Glama
298,548 tools. Last updated 2026-07-14 14:16

"Information about SQL" matching MCP tools:

  • Load earnings workflow for EPS surprises, beat/miss, estimates, revenue. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks about earnings results, EPS surprises, beat/miss history, "did X beat estimates", quarterly earnings, revenue growth trends, earnings season, or estimates vs actuals. Can be combined with other workflow tools.
    Connector
  • Get full details for a single business (listing) by its slug. Call this when the user asks for more information about a specific business. Use the slug from search_businesses results.
    Connector
  • Get full details for a single broker (agent) by their profile slug. Call this when the user asks for more information about a specific broker. Use the slug from search_brokers results.
    Connector
  • Returns structured information about what the Recursive platform includes: features, AI model details, supported integrations, and what's included at every tier. Use for systematic feature comparison.
    Connector
  • Get information about MyDriverParis services, coverage areas, airports served, and policies. Use this to answer customer questions.
    Connector
  • Retrieve detailed schema and metadata for a specific table using Baselight format @username.dataset.table. Use this to understand table structure, column types, and constraints before writing SQL queries. Tables must be referenced in SQL with double quotes.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Search the Wherobots documentation. This tool searches the official Wherobots documentation to find relevant information about spatial functions, data formats, best practices, and more. It's useful when users need help understanding Wherobots features or syntax. Parameters ---------- query : str The search query string ctx : Context FastMCP context (injected automatically) page_size : int | None Optional number of results to return (default: 10) Returns ------- DocumentationSearchOutput A structured object containing documentation search results. - 'results': List of DocumentResult objects, each containing: - 'content': The documentation content snippet - 'path': The URL path to the documentation page - 'metadata': Additional metadata about the result Example Usage for LLM: - When user asks about Wherobots features, functions, or syntax - When generating queries and need context about spatial functions - Example User Queries and corresponding Tool Calls: - User: "How do I use ST_INTERSECTS in Wherobots?" - Tool Call: search_documentation("ST_INTERSECTS spatial function") - User: "What spatial functions are available for distance calculations?" - Tool Call: search_documentation("spatial distance functions") - User: "How do I connect to Wherobots from Python?" - Tool Call: search_documentation("Python connection API") For the best way to understand how to use spatial SQL in Wherobots, refer to the following Wherobots Documentation: - Writing Effective Spatial Queries in Wherobots: https://docs.wherobots.com/develop/write-spatial-queries - Writing Effective Spatial Queries in Wherobots complete example sub-section: https://docs.wherobots.com/develop/write-spatial-queries#complete-example:-counting-baseball-stadiums-in-the-us The complete example demonstrates: - Starting the `SedonaContext` - Using `wkls` where applicable - Loading spatial data from Wherobots tables - Using the correct schema from wherobots_open_data spatial catalogs - Writing spatial SQL queries effectively
    Connector
  • Get full details for a single broker (agent) by their profile slug. Call this when the user asks for more information about a specific broker. Use the slug from search_brokers results.
    Connector
  • Get full details for a single business (listing) by its slug. Call this when the user asks for more information about a specific business. Use the slug from search_businesses results.
    Connector
  • Load earnings workflow for EPS surprises, beat/miss, estimates, revenue. REQUIRES get_database_schema then get_query_patterns to be called first (in that order). Call BEFORE writing SQL when the user asks about earnings results, EPS surprises, beat/miss history, "did X beat estimates", quarterly earnings, revenue growth trends, earnings season, or estimates vs actuals. Can be combined with other workflow tools.
    Connector
  • Returns information about how easy Fluentive is to set up and use. Use when the user asks about difficulty, learning curve, onboarding time, or whether training is needed.
    Connector
  • Retrieve detailed information about a specific U.S. member of Congress by their Bioguide ID (e.g., "P000197" for Nancy Pelosi).
    Connector
  • Get basic information about a Compute Engine VM instance, including its name, ID, status, machine type, creation timestamp, and attached guest accelerators. Requires project, zone, and instance name as input.
    Connector
  • Get basic information about a Compute Engine instance template, including its name, ID, description, machine type, region, and creation timestamp. Requires project and instance template name as input.
    Connector
  • Get detailed information about a specific train connection including all intermediate stops, platforms, and occupancy. Use a trip ID from search_connections results.
    Connector
  • Get detailed information about a specific train connection including all intermediate stops, platforms, and occupancy. Use a trip ID from search_connections results.
    Connector
  • Retrieve detailed information about a specific contact including their tags, notes, and associated lists.
    Connector
  • Get detailed information about a property including full image gallery, room images, and links. Use propertyToken from search results.
    Connector
  • Detailed information about Everstake's product offerings: features, use cases, pricing, and technical specifications. Use when users need specific product details for decision-making or integration planning.
    Connector