"Understanding RAG (Retrieval-Augmented Generation or related topics)" matching MCP tools:

• plan_resume

  PlanExe

  Resume a failed or stopped plan without discarding completed intermediary files. Plan generation restarts from the first incomplete step, skipping all steps that already produced output files. Use plan_resume when plan_status shows 'failed' or 'stopped' and plan generation was interrupted before completing all steps (network drop, timeout, plan_stop, worker crash). For a full restart or to change model_profile, use plan_retry instead. Only failed or stopped plans can be resumed. Returns PLAN_NOT_FOUND when plan_id is unknown and PLAN_NOT_RESUMABLE when the plan is not in failed or stopped state. Returns PIPELINE_VERSION_MISMATCH when the snapshot was created by a different pipeline version; use plan_retry instead.

  Connector

• troubleshoot_response_code

  Sipflow

  [cost: rag (one embed + one vector search) | read-only, network: outbound to embed model only | rate-limited per IP] Like `lookup_response_code` but augmented: returns the static RFC entry PLUS the top vendor-specific RAG hits for the exact code (and any free-text context the user pasted). When the static entry carries known vendor-specific reason-phrase variants (e.g. 484 + opensips → 'Invalid FROM' from `parse_from.c`), those phrases are folded into the embed query so the right vendor docs surface. Use when the user asks 'why did <vendor> reject this with <code>?' and you want vendor-grounded common causes, not just the RFC text. Especially helpful for fax-rejection paths — 488 / 415 / 606 on a T.38 reinvite (`m=image udptl t38`) is one of the most common 488 variants and the tool surfaces FreeSWITCH `mod_spandsp` / Cisco CUBE / AudioCodes T.38 docs alongside the RFC text. Pair with: `lookup_response_code` first (cheaper); `lint_sip_request` when the code is 4xx and they have the offending request; `compare_sdp_offer_answer` for 488/415 caused by a T.38 reinvite SDP mismatch; `validate_stir_shaken_identity` when the code is 438; `stir_attestation_explainer` for STIR-shaped codes (428/436/437/438/608); `dns_diagnose_sip_target` when the code is 503 / 408 and routing is suspect.

  Connector

• knowledge_query

  DialogBrain

  Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use workspace.search for that.

  Connector

• platform_help

  platform

  Get detailed platform documentation for a specific topic. Call this before building features you haven't used before — it returns the full reference (examples, signatures, common patterns) for one topic at a time. Topics: sw.db, sw.fs, sw.email, sw.ai, sw.env, sw.jobs, sw.queue, sw.logs, auth, payments, deploy, inspect, functions, domains, realtime, cron, billing, dev-prod, feedback, getting-started, setup, common-mistakes, architecture-patterns, troubleshooting (legacy ctx.* topic names still resolve) **Example:** ```json { "topic": "sw.db" } ``` Unknown topics return the list of available topics.

  Connector

• get_available_doc_gens

  Skala — Legal Platform for Startups

  Get the list of legal document templates available for generation on the platform (e.g. NDA, employment agreement, stock purchase agreement). For corporate services like 83(b) filing or registered agent, use get_available_corporate_services instead.

  Connector

• knowledge_query

  dialogbrain

  Answer questions using knowledge base (uploaded documents, handbooks, files). Use for QUESTIONS that need an answer synthesized from documents or messages. Returns an evidence pack with source citations, KG entities, and extracted numbers. Modes: - 'auto' (default): Smart routing — works for most questions - 'rag': Semantic search across documents & messages - 'entity': Entity-centric queries (e.g., 'Tell me about [entity]') - 'relationship': Two-entity queries (e.g., 'How is [entity A] related to [entity B]?') Examples: - 'What did we discuss about the budget?' → knowledge.query - 'Tell me about [entity]' → knowledge.query mode=entity - 'How is [A] related to [B]?' → knowledge.query mode=relationship NOT for finding/listing files, threads, or links — use workspace.search for that.

  Connector

• parliament_search_hansard

  UK Legal Research

  Search Hansard for parliamentary debates, questions, and speeches. Returns contributions from MPs and Lords including date, party, debate title, and text (capped at 3000 chars per contribution). Useful for understanding legislative intent or political context.

  Connector

• link_learnings

  Push Realm

  Create a relationship between two learnings. Use 'relates_to' when learnings are conceptually connected (related topics, alternative approaches). Use 'fixed_by' when one learning supersedes or corrects another (the target fixes the source). Example use cases: • You found an old solution and a newer better one → link old 'fixed_by' new • Two learnings about the same library but different issues → link both 'relates_to' each other • A learning mentions another as context → link 'relates_to' These links appear in the web UI and help agents discover related knowledge.

  Connector

• get_collection_detail

  Remember Me Collections

  Get full details of a published collection including all verse text, references, and topics. Args: collection_id: The collection ID (from browse_collections results).

  Connector

• get-conference-info

  elc-conference-mcp-tickets

  Get details about the ELC Conference 2026 — date, venue, speakers, topics, what's included, and ticket link. Use this when someone asks about the conference.

  Connector

• search_content

  humanMCP — kapoost

  Search across all kapoost's pieces — poems, essays, notes, images. Matches query against title, body, tags, and description. Returns matching pieces with a preview snippet. Use this instead of reading every piece when looking for specific themes, words, or topics.

  Connector

• lookup_sip_header

  Sipflow

  [cost: free (pure CPU, no network) | read-only] Instant lookup of a SIP header by canonical or compact form (e.g. "Via" / "v", "Diversion", "P-Asserted-Identity", "Identity", "Session-Expires"). Returns canonical form, compact alias, RFC anchor, where it appears (request / response / both), cardinality (exactly-one / at-most-one / one-or-more / any), allowed/forbidden URI parameters with RFC citations, short description, and related headers. USE FIRST when the user asks about a specific header they saw in a trace - sub-millisecond, no API cost. The cardinality + paramRules fields surface failure modes (e.g. two From: headers, ;tag= on P-Asserted-Identity) without needing a RAG round-trip. Pair with: `lint_sip_request` to mechanically check a real request against these rules; `search_sip_docs` for vendor-specific or 3GPP P-headers not in the bundled registry.

  Connector

• oauth_discovery

  Tenzro Ledger MCP

  RFC 8414 / RFC 9728 OAuth Authorization Server / Protected Resource Metadata. Returns the same metadata document the AS publishes at `GET /.well-known/openid-configuration`, augmented with AAP-specific extensions (authorization_details_types_supported, aap_claims_supported, dpop_signing_alg_values_supported).

  Connector

• read_guides

  Arcadia Finance

  Get Arcadia workflow guides and reference documentation. Call this before multi-step workflows (opening LP positions, enabling automation, closing positions) or when you need contract addresses, asset manager addresses, or strategy parameters. Topics: overview (addresses + tool catalog), automation (rebalancer/compounder setup), strategies (step-by-step templates), selection (how to evaluate and parameterize strategies).

  Connector

• forum_search

  argo-mcp

  Search forum topics and posts. Supports Discourse search syntax: #category-slug to filter by category, @username to filter by author. Always search before creating a bug report or feature request to avoid duplicates.

  Connector

• list_blog_categories

  Walnai Website MCP

  Lists all Walnai blog categories with their slug, name, and description. Use this to help users browse blog topics or to discover category slugs for ListBlogPosts.

  Connector

• browser_take_screenshot

  DialogBrain

  Capture a PNG screenshot of the page or a specific element. Returns base64-encoded image bytes. Use sparingly — favor browser.snapshot for structured DOM understanding.

  Connector

• retract_skill

  VaultCrux Memory Core

  Retract a previously promoted skill. Sets the Engine artifact's living status to 'retracted', removing it from future retrieval results. Use when a skill is found to be incorrect or outdated.

  Connector

• chunk_text

  Toolora MCP Server

  Use this tool to split long text into smaller, overlapping chunks suitable for embedding, vector storage, or RAG pipelines. Triggers: 'chunk this document for RAG', 'split this into embeddings', 'break this into segments', 'prepare this text for a vector database'. Returns an array of chunks with index, text, character count, and estimated token count. Essential before embedding or storing text in a vector database.

  Connector

• chunk_text

  Toolora

  Use this tool to split long text into smaller, overlapping chunks suitable for embedding, vector storage, or RAG pipelines. Triggers: 'chunk this document for RAG', 'split this into embeddings', 'break this into segments', 'prepare this text for a vector database'. Returns an array of chunks with index, text, character count, and estimated token count. Essential before embedding or storing text in a vector database.

  Connector