Skip to main content
Glama
128,620 tools. Last updated 2026-05-06 03:22

"Search results for 'test'" 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
  • Retrieves AI-generated summaries of web search results using Brave's Summarizer API. This tool processes search results to create concise, coherent summaries of information gathered from multiple sources. When to use: - When you need a concise overview of complex topics from multiple sources - For quick fact-checking or getting key points without reading full articles - When providing users with summarized information that synthesizes various perspectives - For research tasks requiring distilled information from web searches Returns a text summary that consolidates information from the search results. Optional features include inline references to source URLs and additional entity information. Requirements: Must first perform a web search using brave_web_search with summary=true parameter. Requires a Pro AI subscription to access the summarizer functionality.
    Connector
  • Search UK legislation on legislation.gov.uk. Returns ranked results: title, type, year, number, and legislation.gov.uk URL. Use legislation_get_toc to explore structure, then legislation_get_section for provisions.
    Connector
  • Semantic search across the Civis knowledge base of agent build logs. Returns the most relevant solutions for a given problem or query. Use the get_solution tool to retrieve the full solution text for a specific result. Tip: include specific technology names in your query for better results.
    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 MidOS knowledge base for relevant information. Use this as your FIRST tool to discover what knowledge is available. Returns ranked results with titles, snippets, and quality scores. Args: query: Search query (keywords or topic) limit: Max results (1-20, default 5) domain: Filter by domain (engineering, security, architecture, devops, ai_ml) Returns: JSON array of matching atoms with title, snippet, score, and source
    Connector

Matching MCP Servers

Matching MCP Connectors

  • [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 BGPT's database of scientific papers by keyword. Args: query: Search terms (e.g. "CRISPR gene editing efficiency") Short, concise queries are best. English language only. Don't include years or filters — use the days_back and num_results params instead. num_results: Number of results to return (1-100, default 16). First 50 results are free, then billed at $0.01/result for paid users. days_back: Only return papers published within the last N days. api_key: Optional: Your Stripe subscription ID for paid access. Get one at https://bgpt.pro/mcp Returns: Papers with title, DOI, Raw Data, methods, results, quality scores, and 25+ metadata fields.
    Connector
  • Search the user's conversation memory. Returns ranked results with content, source timestamps, and confidence scores. For KNOWLEDGE UPDATE questions ('current', 'now', 'most recent'): make two calls — one with scoring_profile='balanced' and one with scoring_profile='recency' — then use the value from the most recent source_timestamp. For COUNTING questions ('how many', 'total'): results may not be exhaustive — search with varied terms and enumerate explicitly before counting. If all results score below 0.3, reformulate with synonyms or specific entity names from the question.
    Connector
  • Search the MeSH vocabulary for standardized medical terms. Find MeSH (Medical Subject Headings) descriptors to use in precise PubMed searches. Returns MeSH IDs, preferred terms, and scope notes. Args: term: Search term (e.g. 'diabetes', 'heart failure', 'opioid'). limit: Maximum results (default 10).
    Connector
  • <tool_description> Search and discover products, recipes AND services in the Nexbid marketplace. Nexbid Agent Discovery — search and discover advertiser products through an open marketplace. Returns ranked results matching the query — products with prices/availability/links, recipes with ingredients/targeting signals/nutrition, and services with provider/location/pricing details. </tool_description> <when_to_use> Primary discovery tool. Use for any product, recipe or service query. Use content_type filter: "product" (only products), "recipe" (only recipes), "service" (only services), "all" (all, default). For known product IDs use nexbid_product instead. For category overview use nexbid_categories first. </when_to_use> <intent_guidance> <purchase>Return top 3, price prominent, include checkout readiness</purchase> <compare>Return up to 10, tabular format, highlight differences</compare> <research>Return details, specs, availability info</research> <browse>Return varied results, suggest categories. For recipes: show cuisine, difficulty, time.</browse> </intent_guidance> <combination_hints> After search with purchase intent → nexbid_purchase for top result After search with compare intent → nexbid_product for detailed specs For category exploration → nexbid_categories first, then search within For multi-turn refinement → pass previous queries in previous_queries array to consolidate search context Recipe results include targeting signals (occasions, audience, season) useful for contextual ad matching. </combination_hints> <output_format> Markdown table for compare intent, bullet list for others. Products: product name, price with currency, availability status. Recipes: recipe name, cuisine, difficulty, time, key ingredients, dietary tags. Services: service name, provider, location, price model, duration. </output_format>
    Connector
  • Browse published Bible verse collections. Search by keyword, filter by language, sort by popularity. Args: search: Search term to filter by name, description, or publisher name. language: Language code prefix (e.g. "en", "de", "ja", "zh"). ordering: Sort order: -downloads (default), -created, name. limit: Number of results (1-100, default 20). offset: Starting position for pagination.
    Connector
  • Test copy on simulated users, or A/B test two variants head-to-head. Use when choosing between headlines, taglines, value propositions, email subject lines, CTA text, product descriptions, or any written content. For single variant: returns raw persona reactions and monologues. For two variants: returns both sets of raw results side by side for you to compare.
    Connector
  • Search UK companies with flexible filters. Combine name search, postcode, status, incorporation date range, SIC/GICS/ICB codes, accounts category, and company type. Returns enriched results with all SIC codes, GICS/ICB mappings, and address details. Cursor pagination for large result sets.
    Connector
  • Search O*NET occupations by keyword. Returns a list of occupations matching the keyword with their SOC codes, titles, and relevance scores. Use the SOC code from results with other O*NET tools to get detailed information. Args: keyword: Search term (e.g. 'software developer', 'nurse', 'electrician'). limit: Maximum number of results to return (default 25).
    Connector
  • WHEN: developer needs to write or scaffold unit tests for a custom D365 object. Triggers: 'generate tests', 'unit test', 'SysTest', 'write test for', 'scénarios de test', 'test this class'. Generate X++ SysTest unit test code for a CUSTOM D365 F&O object based on functional test scenarios. [!] Only meaningful on custom/extension code (D365_CUSTOM_MODEL_PATH). SysTest tests in D365 are highly context-specific -- a generic template rarely compiles without adaptation. REQUIRED: provide test scenarios in the 'testScenarios' parameter (supplied by the functional consultant). Each scenario becomes a concrete test method with arrange/act/assert. For tables: generates tests for find(), exist(), validateWrite(), initValue(). For classes: generates stubs for each public method listed in scenarios. Uses REAL field names and method signatures from the knowledge base.
    Connector
  • Search Bitrix24 REST docs by natural-language query and return a short plain-text list of matches (method/event/article/app doc) with name, type, and brief description. Use the exact name/title from results when calling details tools. Optional filters: `limit` and `doc_type` (method|event|other|app_development_docs).
    Connector
  • Re-run a previous patent search to get fresh results. Free within 6 months of the original search. Use when the user wants to refresh results or check if new infringers have appeared.
    Connector
  • Universal workspace search: files, links, threads, messages. Runs scopes in parallel and returns sectioned results. Default scope='auto' detects target from query. For files the user created/sent (invoices, generated docs), set file_origin='generated'. Use this for all workspace search; lower-level tools are internal.
    Connector