Skip to main content
Glama
128,728 tools. Last updated 2026-05-06 05:18

"General search for 'es'" matching MCP tools:

  • [Step 1 of cost_check] Returns the cost-estimate tool URL pre-filled with the user's insurance + service if provided, plus the general copay range. The tool URL is a hand-off — the user verifies their plan there for an exact copay. Use when: The user asks "how much does therapy cost?" / "is X insurance covered?" / "what's my copay?" — return both the general range AND the deep-link. Don't use when: The user wants to find a provider — use find_provider (which already filters by accepted insurance). Example: get_cost_estimate({ insurance: 'Aetna', service: '354092' })
    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
  • [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
  • [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
  • 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
  • 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

  • Loads one supported self-assessment into the widget by slug. Use `gad7` for anxiety screening, `phq9` for depression screening, and `who5` for general well-being screening when the user wants to take one of those assessments.
    Connector
  • Edit a file in the solution's GitHub repo and commit. Two modes: 1. FULL FILE: provide `content` — replaces entire file (good for new files or small files) 2. SEARCH/REPLACE: provide `search` + `replace` — surgical edit without sending full file (preferred for large files like server.js) Always use search/replace for large files (>5KB). Always read the file first with ateam_github_read to get the exact text to search for.
    Connector
  • Send a message to Atlas Advisor for lightweight hiring advice (2 credits). Faster and cheaper than atlas_chat, no tool use -- best for general hiring questions. Returns AI response text and a conversation_id. Omit conversation_id to start a new conversation; include it to continue a thread.
    Connector
  • Returns usage statistics for your ThinkNEO API key. Shows calls today, this week, this month, monthly limit, remaining calls, top tools used, estimated cost, and current tier. Works without authentication (returns general info).
    Connector
  • Quick AI visibility scan. Returns three scores: AEO Score (0-100, AI search engine findability), GEO Score (0-100, AI citation readiness), and Agent Readiness Score (0-100, AI agent interaction capability). Also returns AI Identity Card with mention readiness (0-100, predicts how likely AI will mention the brand), detected competitors, business profile (commerce/saas/media/general), and top 5 issues. 67+ checks across 12 categories. Free — no API key needed. Does NOT return per-check details or fix code — use audit_site for full breakdown, fix_site for generated fixes, compare_sites to benchmark against a competitor.
    Connector
  • Check whether a specific property is available for the requested dates. Use this tool after the user has selected a property from search.properties and wants to confirm availability before getting a quote. Do NOT use for general browsing — use search.properties instead. Returns available=true/false with conflict details (blocked dates, existing bookings, active locks) if unavailable.
    Connector
  • WHEN: before modifying an object -- check existing customizations. Triggers: 'extensions de', 'CoC sur', 'qui étend', 'event handlers for', 'customizations of', 'avant de modifier'. Finds ALL extension objects (AxClassExtension, AxTableExtension, AxFormExtension), Chain of Command (CoC) classes, and event handlers for a base object. NOT for general references -- use find_references for that.
    Connector
  • Save a note to your notebook. In agent mode writes to your own notebook by default; agents cannot write to other agents' notebooks. In MCP mode target_agent_id is required. If a note with the same key and scope already exists, it will be updated. Use scope to organize: 'global' for general knowledge, 'thread' for thread-specific context, 'person' for contact-specific info.
    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 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
  • 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
  • Generate a direct upload link for a SINGLE image on a SPECIFIC work. Only use this immediately after creating a work when the user mentioned having an image for it. For general image uploads (user says "upload images," "add photos," etc.), use upload_images instead. Never call this tool in a loop. Never ask about file format.
    Connector
  • Performs web searches using the Brave Search API and returns comprehensive search results with rich metadata. When to use: - General web searches for information, facts, or current topics - Location-based queries (restaurants, businesses, points of interest) - News searches for recent events or breaking stories - Finding videos, discussions, or FAQ content - Research requiring diverse result types (web pages, images, reviews, etc.) Returns a JSON list of web results with title, description, and URL. When the "results_filter" parameter is empty, JSON results may also contain FAQ, Discussions, News, and Video results.
    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