Skip to main content
Glama
137,112 tools. Last updated 2026-05-21 12:42

"Information about Query Futures or Future Contracts" matching MCP tools:

  • Execute a SQL query on Baselight and wait for results (up to 1 minute). The query executes and returns the first 100 rows upon completion, or info about a pending query that needs more time. Use DuckDB syntax only, table format "@username.dataset.table" (double-quoted), SELECT queries only (no DDL/DML), no semicolon terminators, use LIMIT not TOP. If query is still PENDING, use `sdk-get-results` to continue polling. If totalResults > returned rows, use `sdk-get-results` with offset to paginate.
    Connector
  • Returns information about safety features on Makuri, including age verification, content filtering, parental controls, and AI safety guardrails. Use when the user asks about child safety, content moderation, or how Makuri protects minors.
    Connector
  • Schedule a snapshot for future execution. Requires: API key with write scope. Max 3 pending schedules per site. Args: slug: Site identifier scheduled_at: ISO 8601 datetime (must be in the future) description: Optional description (max 200 chars) Returns: {"id": "uuid", "scheduled_at": "iso8601", "status": "scheduled"} Errors: VALIDATION_ERROR: Invalid datetime, not in future, or too many pending
    Connector
  • General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    Connector
  • General search tool. This is your FIRST entry point to look up for possible tokens, entities, and addresses related to a query. Do NOT use this tool for prediction markets. For Polymarket names, topics, event slugs, or URLs, use `prediction_market_lookup` instead. Nansen MCP does not support NFTs, however check using this tool if the query relates to a token. Regular tokens and NFTs can have the same name. This tool allows you to: - Check if a (fungible) token exists by name, symbol, or contract address - Search information about a token - Current price in USD - Trading volume - Contract address and chain information - Market cap and supply data when available - Search information about an entity - Find Nansen labels of an address (EOA) or resolve a domain (.eth, .sol)
    Connector
  • Record how a specific household member felt about a recipe. Use to track "who loved it" data, which improves future meal suggestions. Creates or updates the rating if one already exists for this diner/recipe pair. Get recipe IDs from get_recipes and diner IDs from get_household first.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Create and manage cinematic AI video renders through the Future Video Studio Agent API.

  • SAM.gov federal contracts: search, details, AI bid analysis. 33k+ live opportunities.

  • Returns general information about the Makuri platform, including mission, target users, founding details, and company information. Use this tool when the user asks 'what is Makuri', 'who made it', or wants a general overview.
    Connector
  • Use this whenever a user asks about posts they have lined up, queued for a future date, scheduled tomorrow, coming up next week, or similar wording. Prefer relative_range for natural language dates such as today, tomorrow, next_7_days, next_30_days, this_week, or next_week. Use date for an exact local YYYY-MM-DD day, or scheduled_from/scheduled_until for an explicit ISO range.
    Connector
  • Query real data from a dataset. Check instructions for featured dataset_ids and NOTES section for common filter patterns (municipal budgets, contracts, weather, energy, fuel prices).
    Connector
  • Query the DezignWorks knowledge base for information about the product, troubleshooting, features, workflows, supported hardware, and licensing. DezignWorks is reverse engineering software that integrates with SolidWorks and Autodesk Inventor, converting 3D scan data and probe measurements into parametric CAD models. Use this tool when answering questions about the product's capabilities, compatibility, or how to accomplish specific tasks.
    Connector
  • After executing a task, store the result so future identical or similar tasks return a cache hit via dedupq_check. Costs 2 credits.
    Connector
  • Use answer_query to get a grounded answer to a query about Google developer products. This tool has limited quota. This tool will synthesize information from the corpus to generate an answer to the query. answer_query grounds answers using the same corpus as search_documents. If you get a 429 out of quota error, use search_documents instead.
    Connector
  • Get information about an NFT collection or a specific token within a collection. If token_id is provided, returns token-level details (owner, URI). If omitted, returns collection-level info (name, symbol, total supply).
    Connector
  • IMPORTANT: Always use this tool FIRST before working with Vaadin. Returns a comprehensive primer document with current (2025+) information about modern Vaadin development. This addresses common AI misconceptions about Vaadin and provides up-to-date information about Java vs React development models, project structure, components, and best practices. Essential reading to avoid outdated assumptions. For legacy versions (7, 8, 14), returns guidance on version-specific resources.
    Connector
  • Retrieve detailed information about a specific U.S. member of Congress by their Bioguide ID (e.g., "P000197" for Nancy Pelosi).
    Connector
  • Get bytecode at an address on Ethereum mainnet. Returns "0x" for EOAs (wallets), non-empty hex for contracts. Use to determine if an address is a contract or EOA, and to retrieve deployed bytecode.
    Connector
  • Get detailed information about a specific match, including compatibility grade, strengths, concerns, and — if both parties accepted — the counterparty's contact information.
    Connector
  • BEST FOR QUESTIONS. Ask any question about probabilities or future events. Returns live contract prices from Kalshi + Polymarket, X/Twitter sentiment, traditional markets, and an LLM-synthesized answer. No auth required.
    Connector
  • Get comprehensive information about an address, including: - Address existence check - Native token (ETH) balance (provided as is, without adjusting by decimals) - First transaction details (block number and timestamp) for age calculation - ENS name association (if any) - Contract status (whether the address is a contract, whether it is verified) - Proxy contract information (if applicable): determines if a smart contract is a proxy contract (which forwards calls to implementation contracts), including proxy type and implementation addresses - Token details (if the contract is a token): name, symbol, decimals, total supply, etc. Essential for address analysis, contract investigation, token research, and DeFi protocol analysis.
    Connector
  • Lists scheduled queries configured in the project's BigQuery. **What is a scheduled query?** A scheduled query is a SQL query automatically executed on a defined schedule in BigQuery. It is used to aggregate data, populate reporting tables, or perform recurring transformations. **When to use this tool:** - When the user EXPLICITLY asks about scheduled queries, BigQuery pipelines, or transfer configs - When the user asks "what are my scheduled queries?", "my BigQuery pipelines" - To check execution frequency or status of a specific scheduled query **Do NOT use this tool** for general data queries, analytics, or when the user asks about page views, metrics, or data from connectors. Use get_schema_context + execute_query instead. **Available filters:** - dataset: filter by destination dataset (e.g., 'prod_reports') - status: filter by status 'active' (enabled) or 'disabled' **Response format:** Returns a JSON with for each scheduled query: its name, SQL query, execution schedule, destination dataset, status (active/disabled), and last/next execution dates.
    Connector