Skip to main content
Glama
114,467 tools. Last updated 2026-04-21 14:35
  • Search documents. Returns ranked results with title, author, year, description, url, id, score — not full content. Use URLs from results with fetch/browsing to read actual documents. Use when: user asks to research, find papers/books/articles, look up facts, find discussions, legal cases, or any "search for..." request. Strategy: use 2-4 keywords per query (English preferred). Pick the right type first. Try synonyms if few results. Search across multiple types to cross-reference. Use detail() for full metadata on promising results.
    Connector
  • Find people in the organization who can be sent documents for signature or acknowledgment. Search by name or email.
    Connector
  • Find documents available to send for employee signatures or policy acknowledgments. Use this to browse what documents the organization has ready to send.
    Connector
  • Search for relevant documentation. Use `list-categories` first to see available categories. Filter by query text, framework, phase, feature, category, or tags. Returns documents sorted by relevance.
    Connector
  • Search across 3GPP and IETF specification documents using full-text search. Returns ranked results with content previews.
    Connector
  • Search Google Patents for patent documents and scholarly articles. Returns patent titles, IDs, inventors, assignees, filing dates, and abstracts.
    Connector

Matching MCP Servers

Matching MCP Connectors

  • 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
  • Search the regulatory corpus using keyword / trigram matching. Uses PostgreSQL trigram similarity on document titles and summaries. Returns documents ranked by relevance with summaries and classification tags. Prefer list_documents with filters (regulation, entity_type, source) first. Only use this for free-text keyword search when structured filters aren't sufficient. Args: query: Search terms (e.g. 'strong customer authentication', 'ICT risk', 'AML reporting'). per_page: Number of results (default 20, max 100).
    Connector
  • Ask a question and get a synthesized answer from the knowledge base. Unlike search (which returns raw atoms), ask synthesizes a natural-language answer by combining relevant sources. Use when you need an explanation, not just matching documents. Args: question: Your question (e.g., "How do I implement caching in FastAPI?")
    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
  • Query SEC filings and financial documents from US capital markets and exchanges. This tool searches through 10-K annual reports, 10-Q quarterly reports, 8-K current reports, proxy statements, earnings call transcripts, investor presentations, and other SEC-mandated filings from US companies. Use for questions about US company financials, executive compensation, business operations, or regulatory disclosures. Limited to official SEC filings and related documents only.
    Connector
  • Get recently published or updated regulatory documents. Shortcut for 'what is new this week' - returns documents from the last N days, sorted by publication date (newest first). Useful for weekly regulatory briefings. Args: days: Look back N days (default 7). entity_type: Filter by entity type code. regulation: Filter by regulation family code. urgency_max: Only include items at or above this urgency (1=critical, 2=high, etc.).
    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
  • 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
  • Search for data rows in a dataset using full-text search (query) or precise column filters. Returns matching rows and a filtered view URL. Use to retrieve individual rows. Do NOT use to compute statistics — use calculate_metric or aggregate_data instead.
    Connector
  • Search for solutions other agents already discovered. STOP and search before acting on any error — even mid-task. Do not chain fixes without searching each one. When: Any error, compile failure, stack trace, or unexpected output. Before config, integration, or setup tasks. When a fix attempt just failed — search before trying the next one. Unfamiliar library or framework combination. Do not skip because the fix seems obvious — obvious fixes are the most common and most likely to already be solved. How: Paste the exact error message, not your goal. Include framework or language name. Read failedApproaches first to skip dead ends. Feedback: Include previousSearchFeedback to rate a result from your last search — this refunds your search credit and costs nothing extra.
    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
  • 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
  • Browse regulatory documents with filters and pagination. Returns a paginated list of documents with summaries, tags, doc_purpose (regulation_text, enforcement, reference, irrelevant), and doc_jurisdictions (e.g. ['eu'], ['fi'], ['de']). Use this for filtered browsing (e.g. all DORA documents from the last 30 days). Use search_regulations instead when you have specific keywords to search for. Args: source: Filter by data source code: eur_lex, eba, esma, eiopa, finfsa, bafin. regulation: Filter by regulation family code: dora, mica, aml, mifid2, crd_crr, psd, csrd, sfdr, ai_act, emir, solvency, idd, gdpr. entity_type: Filter by entity type: credit_institution, payment_institution, e_money, investment_firm, fund_manager, aifm, insurance, pension, crypto_service, crowdfunding, credit_servicer. urgency_max: Max urgency level (1=critical, 2=high, 3=medium, 4=low, 5=informational). E.g. 2 returns only critical and high urgency items. days: Only return documents from the last N days (1-365). page: Page number (default 1). per_page: Results per page (default 20, max 100).
    Connector
  • Search for data rows in a dataset using full-text search (query) or precise column filters. Returns matching rows and a filtered view URL. Use to retrieve individual rows. Do NOT use to compute statistics — use calculate_metric or aggregate_data instead.
    Connector
  • Search or fetch posts from the MetaMask Embedded Wallets community forum (builder.metamask.io). Use for troubleshooting real user issues, finding workarounds, and checking if an issue is known. Provide a query to search or a topic_id to read the full discussion.
    Connector
  • Search Companies House by company name. Returns a list of matches. For a direct lookup by company number, use the company://{company_number} resource instead (e.g. read_resource("company://00445790")).
    Connector
  • Search for a token's CoinGecko coin ID by name, symbol, or contract address. Use this first if you're unsure of the correct coin_id for scan_token or validate_trade. Example: search 'pepe' to find the correct coin ID.
    Connector
  • Rate a search result. Use feedbackActions from search results — they have pre-built params ready to pass. When: After trying a search result (useful or not_useful), or immediately if a result doesn't match your search (irrelevant). - "useful" — tried it, solved your problem - "not_useful" — tried it, didn't work (reason REQUIRED: what you tried and why it failed) - "irrelevant" — doesn't relate to your search (you did NOT try it)
    Connector
  • Search for local businesses. Returns name, category, city, country, logo_url, available_details (what data exists), and scores. Check available_details to see what is available, then call get_business for full details.
    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
  • Search the web using Bing. Returns organic results, related searches and more. Alternative to Google for web search with different ranking algorithms and results.
    Connector
  • [Read] Search and analyze X/Twitter discussions for a topic, with tweet-level evidence and cited posts. Aggregate social mood, sentiment score, or positive/negative split -> get_social_sentiment. Open-web pages -> web_search. Multi-platform social search -> search_ugc.
    Connector
  • Get Lenny Zeltser's expert writing guidelines for security reports and assessments. Provides guidance on tone, structure, clarity, executive summaries, and avoiding common writing mistakes. Works for any security document. Your documents are never sent to this server—guidelines flow to your AI for local analysis. Note: For incident response reports specifically, use the ir_* tools which provide deeper section-by-section review criteria.
    Connector
  • Get HIPAA Agent verified reputation stats — total scans, unique practices, documents generated, breaches tracked, uptime, and SHA-256 data integrity hash. Free, no authentication required.
    Connector
  • Generate a signed URL for a screenshot that can be used without an API key. Useful for embedding screenshots in emails, documents, or sharing with third parties. Signing is free, rendering the URL consumes one credit. URLs expire after the specified duration.
    Connector
  • Search XPay Hub for paid API services. Use this PROACTIVELY when the user asks you to: search the web, find emails, enrich contacts/companies, verify emails, find similar websites, extract web page content, get company news, search for people by title/company, get job postings, generate images, or any data lookup task. Returns matching servers with slugs, tool counts, and pricing. Use xpay_details next to see the full tool list for a server.
    Connector
  • Convert HTML or Markdown to a pixel-perfect PDF. Returns JSON: { url } — a temporary download URL (valid ~1 hour). Great for generating invoices, reports, receipts, or formatted documents programmatically. Supports full HTML/CSS including tables, images (base64 or URL), and inline styles. For Markdown input, set format='markdown'. 50 sats per conversion. Use convert_file instead for converting existing files between formats (e.g., DOCX→PDF). Pay per request with Bitcoin Lightning — no API key or signup needed. Requires create_payment with toolName='convert_html_to_pdf'.
    Connector
  • List sites in the index that expose a live MCP server, ranked by agentic readiness. Use this when your agent needs to discover callable MCP endpoints for a domain ('payments', 'jobs', 'search') or overall. Pairs naturally with verify_mcp for a probe-before-use workflow.
    Connector
  • Search a company's knowledge base for policies, procedures, and documentation. First use lookup_company to get the tenant_id, then use this tool to search their 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
  • List all documents in a deal's data room. Shows what files and content have been uploaded for a deal, along with their processing status. Args: deal_id: The deal ID (from sieve_deals or sieve_dataroom_add).
    Connector
  • Search DevExpress documentation for a given technology and a question. If you want to search for multiple technologies, pass them as a list. This tool returns only snippets/excerpts; full content requires a follow-up `devexpress_docs_get_content` call on a chosen URL. ALWAYS call `devexpress_docs_search` before ANY `devexpress_docs_get_content` call in a user request chain.
    Connector
  • Search TED notices using full-text search (BM25 via Tantivy). Best for keyword matching and exact phrase searches. Args: query: The search query string limit: Maximum number of results (default: 10) procurement_type: Filter by procurement type (optional) Returns: Search results ranked by BM25 text relevance
    Connector
  • Search ENS names using natural language. Supports all query types: - Filtered search: "4-letter words under 0.1 ETH" - Concept search: "ocean themed names" (semantic similarity across 3.6M names) - Creative search: "names for a coffee brand" (AI-generated suggestions) - Collection search: "crypto terms expiring soon" - Activity: "what sold recently?" - Availability check: "is coffee.eth taken?" - Bulk check: "check apple.eth, banana.eth, cherry.eth" Returns structured results with name, price, owner, tags, and availability info.
    Connector
  • Search for nodes by property values in a deployed graph project. Supports exact match and contains search (prefix value with ~ for contains). Examples: Exact: filters: {"name": "Alan Turing"} Contains: filters: {"name": "~turing"} (case-insensitive) Combined: entity_type: "person", filters: {"field": "~physics"} Without entity_type, searches ALL node types.
    Connector