Skip to main content
Glama
198,237 tools. Last updated 2026-06-13 05:59

"Search for 'fodda'" matching MCP tools:

  • Search the web for current information on any topic. Returns extracted page content, not just snippets. Best for factual lookups, specific questions, or when you need a list of sources. For open-ended questions that need synthesis across many sources, use the research tool instead. For news queries (current events, breaking news, politics, world events), set topic="news" to search news sources specifically. This returns recent articles with publication dates. Set include_answer=true to get an AI-synthesized answer alongside results (adds 5 credits). This is the sweet spot for most agent tasks, e.g. basic + include_answer = 8 credits, much cheaper than a full 25-credit research call. Returns: query, answer (if requested), results (array of {title, url, content, description, fetched, published_date}), search_depth, topic, elapsed_ms, credits_used, credits_remaining, altered_query. Args: query: The search query search_depth: "basic" (default) for extracted page content (3 credits), "snippets" for SERP snippets only without page fetching (1 credit) max_results: Number of results (default 10, max 20) include_answer: Generate an AI answer that synthesizes the search results (adds 5 credits) include_domains: Only include results from these domains (max 10) exclude_domains: Exclude results from these domains (max 10) topic: "general" for web search, "news" for news articles. use "news" for current events, breaking news, politics, or any time-sensitive query freshness: Filter by recency - "day", "week", "month", "year", or "YYYY-MM-DD:YYYY-MM-DD"
    Connector
  • Search for medical procedure prices by code or description. Use this for direct lookups when you know a CPT/HCPCS code (e.g. "70551") or want to search by keyword (e.g. "MRI", "knee replacement"). For code-like queries → exact match on procedure code. For text queries → searches code, description, and code_type fields. Supports filtering by insurance payer, clinical setting, and location (via zip code or lat/lng coordinates with a radius). NOTE: Results are from US HOSPITALS only — not non-US providers, independent imaging centers, ambulatory surgery centers (ASCs), or other freestanding facilities. Args: query: CPT/HCPCS code (e.g. "70551") or text search (e.g. "MRI brain"). Must be at least 2 characters. code_type: Filter by code type: "CPT", "HCPCS", "MS-DRG", "RC", etc. hospital_id: Filter to a specific hospital (use the hospitals tool to find IDs). payer_name: Filter by insurance payer name (e.g. "Blue Cross", "Aetna"). plan_name: Filter by plan name (e.g. "PPO", "HMO"). setting: Filter by clinical setting: "inpatient" or "outpatient". zip_code: US zip code for geographic filtering (alternative to lat/lng). lat: Latitude for geographic filtering (use with lng and radius_miles). lng: Longitude for geographic filtering (use with lat and radius_miles). radius_miles: Search radius in miles from the zip code or lat/lng location. page: Page number (default 1). page_size: Results per page (default 25, max 100). Returns: JSON with matching charge items including procedure codes, descriptions, gross charges, cash prices, and negotiated rate ranges per hospital.
    Connector
  • Subscribes the authenticated user to job alerts for a specific saved job search. **Input:** - `job_search_id`: The job search identifier to subscribe to (required). Accepts either the job search UUID or the composite job ID returned by `jobs_search` / `jobs_details` (format: "seo_id--job_search_id"). - `frequency`: Alert frequency — one of daily, weekly, monthly (optional, defaults to "weekly") **Output:** Returns the created or updated job alert with id, status, and frequency. Idempotent: calling this tool for an already-subscribed search updates the existing alert without creating a duplicate.
    Connector
  • [tourradar] Search for tours by title using AI-powered semantic search. Returns a list of matching tour IDs and titles. Use this when you need to look up a tour by name. When you know tour id, use b2b-tour-details tool to display details about specific tour
    Connector
  • Search FTIR.fun public result pages (community-shared analyses). USE WHEN: - User asks "has anyone analyzed material X?" - Looking for prior analysis examples or case studies - Research community knowledge lookup - Want to see how others interpreted similar spectra DO NOT USE: - For new spectrum analysis (use search_ftir_library instead) - For library database search (use search_ftir_library instead) - When user provides their own spectrum data INPUT: - query: search text (e.g., "polyethylene", "PET", "pharmaceutical") OUTPUT: - results: list of public result pages with: * id: result identifier (use with fetch) * url: direct link to result page * title: result headline * text: summary of analysis * metadata: additional info (result_num, source) EXAMPLE: >>> search(query="polyethylene terephthalate")
    Connector
  • POST /v1/contact/search. Search for contacts at specified companies. Returns a job_id (async, 202). enrich_fields required (at least one of contact.emails or contact.phones). Use company_list (slug) instead of domains to search a saved list.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • Give your AI agent a phone. Place outbound calls to US businesses to ask, book, or confirm.

  • Cloudflare Workers MCP server: embedding-search

  • [tourradar] Search tour reviews using AI-powered semantic search. Requires tourIds to scope results to specific tours. Use this when the user asks about reviews, feedback, or experiences for specific tours. Combine with an optional text query to find reviews mentioning specific topics (e.g., 'food', 'guide', 'accommodation'). When you don't have tour IDs, use vertex-tour-search or vertex-tour-title-search first to find them.
    Connector
  • Search MCP servers by server title/name, description, or by the tools they provide. Accepts natural language capability queries like 'send emails', 'search the web', 'create pull requests', or direct server names like 'GitHub' or 'Stripe'. Results are ranked by relevance: title match first, then tool name match, then description. Each result includes the server's tool list so you can confirm it does what you need. Set limit based on the type of request you received: - Prompting (general/exploratory — user is browsing or asking broadly): use 20-30 - Task assignment (user delegated a goal for you to execute autonomously): use 10-15 - Instruction/directive (specific command with a clear target server in mind): use 3-5
    Connector
  • Search across ALL networks for tokens, pools, and DEXes by name, symbol, or address. Good starting point when you don't know the specific network. Returns three named arrays: tokens, pools, dexes. NOTE: In `pools[]`, the DEX factory contract address is exposed under `factory_id` (matching `getPoolDetails` and `getPoolTransactions`). Use `dex_name` if you need a human-readable label.
    Connector
  • AI/LLM-optimized web search built for RAG: returns a synthesized natural-language answer plus a ranked list of sourced results (title, url, content snippet, relevance score). Prefer this over scraping a generic search engine when you need grounded, citable web context. Example: search({ query: "latest SpaceX Starship test result" })
    Connector
  • "Find [disease / drug / gene target]" / "Open Targets lookup for [name]" / "what's the Open Targets ID for [X]" — text search across diseases, drug targets, and drugs in the Open Targets Platform (the leading drug-discovery knowledge graph). Returns ranked matches with their canonical IDs (ENSG... for targets, EFO_... for diseases, CHEMBL... for drugs). Use first to find IDs, then call target/disease/drug for details.
    Connector
  • Search for drugs in RxNorm (Normalized names for clinical drugs). Use this tool to: - Find drug concepts by brand or generic name - Look up medications for prescribing - Search for drug formulations Returns matching drugs with RxCUI identifiers, names, and term types.
    Connector
  • Search Twitter/X. Returns a compact human-readable list by default; pass format='json' for full structured data. Use glim_twitter_get(ref) for full thread context. Use docs://search-operators for reference.
    Connector
  • [tourradar] Use this when you need to find city IDs for tour search filters like start city, end city, or cities to visit. Searches for cities by name within a specific country. Supports multiple name variants to handle different spellings (e.g., Krakow, Kraków, Cracow).
    Connector
  • OpenAI deep-research / company-knowledge compatibility. Search Cyclesite's active UK used-bike listings by free-text query (matches title, brand, model). Returns the canonical OpenAI shape: { results: [{ id, title, url }] }. Use the id to call fetch() for the full document.
    Connector
  • OpenAI ChatGPT Deep Research / Connectors search contract. Returns matching Dynamoi artists, campaigns, and Smart Links so they can be cited in a deep-research session. For regular ChatGPT chat use dynamoi_search instead.
    Connector
  • Unified colony search in ONE call: your own + public/shared MEMORY (hybrid semantic + keyword — C1-private, never another agent's private data) AND the public WALL feed. Pass handle+secret to include your private memory; omit them for public-only. Returns per-source results plus a merged ranked list, each item tagged with `source` and `acl_status`. This is 'search your past and your colony'.
    Connector
  • Search HuggingFace Hub for ML models. Specify a keyword (e.g. 'bert', 'llama', 'stable diffusion') and optional task filter (e.g. 'text-classification', 'text-generation', 'image-classification'). Returns top results sorted by downloads or likes, including model ID, author, pipeline task, framework library, download count, likes count, and tags.
    Connector