Skip to main content
Glama
134,483 tools. Last updated 2026-05-23 13:30

"Search or general inquiry" matching MCP tools:

  • 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
  • Create a new forum topic (bug report, feature request, or general discussion). Always call forum_search first to check for duplicates. Call forum_list_categories to get the correct categoryId.
    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
  • Return the first-party Cannon Studio checkout or inquiry URL for a selected offering. Public read-only: no auth, no state changes, no charges; use list_offerings first to get a valid product_key.
    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
  • [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

Matching MCP Servers

Matching MCP Connectors

  • Brave Search MCP — independent web index (no Google/Bing dependency)

  • 4 web-search tiers (x402 USDC on Base) - simple/medium/deep/cached. Free health.

  • 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
  • Send a general inquiry to a local service business. Use this when the customer has a question, needs a custom quote, or wants to describe an issue that doesn't fit a specific bookable service. The business owner will be notified immediately via SMS and will contact the customer directly. ONLY call this if the business has 'inquiry' in its enabledFeatures array.
    Connector
  • Deploy an agent from a template (28 general + 9 vertical). Creates agent + skills + tools + grading suite in one shot. Use kopern_list_templates to see available slugs.
    Connector
  • Book a handyman for general home repairs: furniture assembly, TV mounting, drywall patching, door fixes, minor plumbing fixtures, and similar non-specialist tasks. Returns a confirmed booking. Call /quote first.
    Connector
  • Execute a search and return ranked Markdown results (title, URL, snippet). ## Two modes ### Mode 1 — General web search (no list_domains needed) Omit domain and sub_domain entirely. Use when the query is open-ended and does not target a specific structured data source. Example: search(query="what is quantum computing") ### Mode 2 — Vertical search (call list_domains first) Use when the query targets a specific domain: stocks, patents, flights, CVEs, weather, academic papers, etc. Steps: 1. Call list_domains to get the sub_domain and mandatory query format for the target domain. 2. Pass domain + sub_domain from list_domains output. Never guess them. 3. Format query exactly as specified in the query_format column — wrong format = wrong results. **IMPORTANT: For any query that may belong to a supported vertical domain, ALWAYS call list_domains first — vertical search produces significantly better results than general web search.** ## Decision rule — which mode to use Use Mode 2 (vertical) when ANY of these apply: - Query involves a ticker, DOI, CVE, IATA code, patent number, address, or other structured identifier - Query targets a specific vertical: finance, legal, academic, security, travel, geo, environment, etc. - User asks for real-time or specialized data (stock price, weather, flight status, drug info, etc.) Use Mode 1 (general) when the query is purely conversational or open-ended with no structured lookup. ## After getting results — when to call extract Search returns titles + snippets only. Call extract when: - The snippet is truncated or insufficient to answer the question - User asks to read, summarize, or get details from a specific URL - You need to verify a claim or fact from the source page - The answer requires data only visible in the page body (tables, sections not in snippet) ## Query decomposition One intent per search call. For 2–5 independent queries use batch_search instead. WRONG: search(query="AAPL price and earnings and analyst rating") RIGHT: batch_search(queries=[{query:"AAPL price",...}, {query:"AAPL earnings",...}])
    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
  • Get open support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). # fetch_open_tickets ## When to use Get open support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). ## Parameters to validate before calling - search (string, optional) — Search by subject or description (case-insensitive) - platform (string, optional) — Filter by platform: renaissance, api, general, overture, winners - priority (number, optional) — one of: 1, 2, 3 — Filter by priority: 1 (Low), 2 (Medium), 3 (High) - page (number, optional) — Page number for pagination (default: 1, 20 tickets per page)
    Connector
  • Searches Brave's Place Search API. A single call may populate any combination of `results` (POIs), `cities`, `addresses`, `streets`, and `location` (the resolved search area), depending on the query shape. Use for POIs near coordinates or a named area, browsing general POIs (omit `query`, supply coords or `location`), disambiguating bare city names, resolving specific addresses, or looking up streets. Anchor via `latitude`+`longitude` or `location`; with neither, `query` is required.
    Connector
  • Get closed/resolved support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). # fetch_closed_tickets ## When to use Get closed/resolved support tickets with pagination (20 per page) and search. Returns summary info only — use get_ticket with the case number to get full ticket details including notes, files, and collaborators. Supports filtering by subject/description text, platform (renaissance, api, general, overture, winners), and priority (1=Low, 2=Medium, 3=High). ## Parameters to validate before calling - search (string, optional) — Search by subject or description (case-insensitive) - platform (string, optional) — Filter by platform: renaissance, api, general, overture, winners - priority (number, optional) — one of: 1, 2, 3 — Filter by priority: 1 (Low), 2 (Medium), 3 (High) - page (number, optional) — Page number for pagination (default: 1, 20 tickets per page)
    Connector
  • Search the web via Brave Search API with local QVAC LLM cleaning. Returns cleaned markdown summaries. Use for general web research, factual lookups, and topic exploration.
    Connector
  • Use this when the user mentions a place, neighbourhood, landmark, or area but does not give exact coordinates. Examples: 'near the Louvre', 'in Trastevere', 'around Times Square', "walking distance from St Paul's Cathedral". Returns experiences matched first by exact venue/neighbourhood, then by city centre fallback. Do not use for general city-wide search; use search_experiences for that.
    Connector
  • Search user memories by keyword, type, tags, or date range. With query: Case-insensitive keyword search on content. Without query: Returns memories by recency. Use type filter to search only facts or only moments.
    Connector
  • Search across all Koalr entities: developers (by name or GitHub login), repositories (by name), pull requests (by title or branch), and teams (by name). Use this when you need to find an entity before using a more specific tool. Read-only.
    Connector