Skip to main content
Glama
728,116 tools. Updated 2026-10-31 09:38

"A tool for finding documentation for code" matching MCP tools:

  • Look up a NUCC provider taxonomy code (the specialty codes used on HIPAA transactions + NPI registrations) or search by keyword. Returns classification + type + optional specialization. Source: NUCC Health Care Provider Taxonomy Code Set (public; CMS-accepted). WHEN TO USE: Resolving a NUCC provider taxonomy code to its specialty description. WHEN NOT: For finding a provider by specialty in a region (not yet implemented).
    ConnectorNo auth
  • Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.
    ConnectorNo auth
  • Retrieve the complete markdown of one documentation article by the id returned from `search` (for example `en/claude-code/advanced-techniques/hooks-automation`). The text is returned in full; `metadata.gated` only reports whether the article sits behind the paywall on the web. An unknown id is an error — call `search` first.
    ConnectorNo auth
  • Record that a rule was checked against the current state of things (code, data, documentation) and still holds. Rules lose confidence over time and low-confidence rules are queued for review. Affirming resets the rule's staleness clock and restores its confidence to the configured maximum, taking it out of the review queue. It is meant for rules actually verified as correct, not for rules that were merely retrieved or look plausible. Args: rule_id: UUID of the verified rule.
    ConnectorAPI key
  • Extracts fine-grained deltas between previous text/document state and updated state, and crystallizes them into the Volumetric Memory lattice in sub-2ms on CPU with automatic secret scrubbing and SHA-256 deduplication. Use this tool for continuous incremental sync of code files, documentation, PRDs, and database schemas. Mutating operation. Requires X-License-Key authentication.
    ConnectorNo auth
  • Extracts fine-grained deltas between previous text/document state and updated state, and crystallizes them into the Volumetric Memory lattice in sub-2ms on CPU with automatic secret scrubbing and SHA-256 deduplication. Use this tool for continuous incremental sync of code files, documentation, PRDs, and database schemas. Mutating operation. Requires X-License-Key authentication.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • Keyless. Resolve a structured Apier compliance error code into a Norwegian-bokmål Explanation envelope: summary, bokmål why, ordered fix_steps, optional documentation link + legal_basis, and an optional handover block (who / where / what / why) for errors a human must resolve (e.g. AUTH_INSUFFICIENT_ROLE, AUTH_NO_DELEGATION, SCOPE_MISSING) — agent-resolvable errors ship `handover: null`. Accepts any code from the closed EXPLAINER_ERROR_CODES catalogue. Optional flat context_org_number / context_scope / context_role / context_field / context_upstream_system strings carry placeholder values interpolated into the bokmål text; missing values fall back to 'ukjent <noun>'. Failure modes: VALIDATION_FAILED on an unknown code; a credential without `read:rulebook` can't see the tool; a call returns unknown tool (-32602). For a company's live obligations rather than an error explanation, use get_company_obligations instead. Docs: https://www.apier.no/docs/guides/error-handling
    ConnectorNo auth
  • Search detailed documentation for Strudel live coding or ABC/ABCJS notation. Returns relevant code examples and explanations from the official docs. Use this when the curated guides (get-strudel-guide, get-music-guide) don't cover what you need — for specific functions, advanced techniques, or when you're unsure about syntax. Powered by semantic search over strudel.cc and ABCJS docs.
    ConnectorNo auth
  • Identifies and ranks top domain authorities, leading researchers, and primary documentation repositories for technical topics. Use when finding primary source experts to cite or discovering foundational documentation for specialized fields; for ranking general search query snippets, use synthesize_neural_search instead. Stateless read-only edge call (max 32 KB, 60 RPM): accepts 'subject_area' ('authority_metric' defaults to 'pagerank_and_domain_authority'), supports '?demo=true' or L402 (10 sats), and returns HTTP 400 if invalid.
    ConnectorNo auth
  • Search across the SiteGPT Docs knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about SiteGPT Docs, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).
    ConnectorNo auth
  • Get remediation advice for a single finding as GitHub-flavored markdown. When AI Assist is enabled and within budget this is a suggestion written for this exact finding; otherwise it falls back to the static guidance-library text and says so in 'source'. Unlike the other reads this one can spend AI budget, which is why it is a separate tool. Use this for advice on one finding; for the whole library use list_security_guidance. Requires project context.
    ConnectorAPI key
  • Return the QuillAI developer documentation as markdown for agents that need to write integration code. Omit `topic` to get a short index (~500 words) with section titles. Pass `topic: "all"` for the full concatenated docs (~8k words). Pass `topic: "<section>"` (e.g. "authentication", "webhooks", "structured output") to get just that section.
    ConnectorOAuth
  • [docs.mzizi.dev] Search across the Mzizi knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about Mzizi, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).
    ConnectorNo auth
  • Fetches one public HTTP/HTTPS page and returns its primary readable content as Markdown. Use this for article or documentation body text without page chrome. It does not run JavaScript; use a browser tool for client-rendered pages. Native text/markdown responses are preserved. Limit: 8 s, 5 redirects, 768 KiB remote body, 150k output characters.
    ConnectorNo auth
  • BUILDER TOOL — fetches the full markdown content of any Yield.xyz documentation page. Use after yield_lookup_docs returns a URL. Returns authoritative spec with exact field names, types, and examples. Only accepts docs.yield.xyz URLs. Do NOT use this for live API calls or user transactions.
    ConnectorNo auth
  • Stores text documents, code snippets, architectural decisions, and factual knowledge into persistent long-term memory partitioned by space_id. Use this tool when saving important facts, project conventions, API keys, user preferences, or documentation for future sessions. Do NOT use for retrieving stored memory (use icx_recall_scoped for semantic QA, icx_search_facts for keyword lookup, or icx_quote_slot for verbatim quotes). Ingestion is additive and non-destructive: creates new memory nodes without overwriting or mutating existing records. Requires X-License-Key authentication.
    ConnectorNo auth
  • Stores text documents, code snippets, architectural decisions, and factual knowledge into persistent long-term memory partitioned by space_id. Use this tool when saving important facts, project conventions, API keys, user preferences, or documentation for future sessions. Do NOT use for retrieving stored memory (use icx_recall_scoped for semantic QA, icx_search_facts for keyword lookup, or icx_quote_slot for verbatim quotes). Ingestion is additive and non-destructive: creates new memory nodes without overwriting or mutating existing records. Requires X-License-Key authentication.
    ConnectorNo auth
  • USE WHEN discovering what Pine Script v6 documentation is available. Returns a categorised list of doc file paths with one-line descriptions. AFTER calling this tool, call get_doc(path) for small files or list_sections(path) then get_section(path, header) for large files (ta.md, strategy.md, collections.md, drawing.md, general.md). Data sourced from bundled Pine Script v6 documentation.
    ConnectorNo auth
  • USE WHEN reading the full content of a Pine Script v6 documentation file. Returns the file content; when limit is set, a header shows the char range and offset to continue reading. AFTER calling this tool, use offset=<end> to continue if the header indicates more content is available. For large files (ta.md, strategy.md, collections.md, drawing.md, general.md), prefer list_sections() + get_section() instead. Data sourced from bundled Pine Script v6 documentation.
    ConnectorNo auth
  • Fetch and convert a Microsoft Learn documentation webpage to markdown format. This tool retrieves the latest complete content of Microsoft documentation webpages including Azure, .NET, Microsoft 365, and other Microsoft technologies. ## When to Use This Tool - When search results provide incomplete information or truncated content - When you need complete step-by-step procedures or tutorials - When you need troubleshooting sections, prerequisites, or detailed explanations - When search results reference a specific page that seems highly relevant - For comprehensive guides that require full context ## Usage Pattern Use this tool AFTER microsoft_docs_search when you identify specific high-value pages that need complete content. The search tool gives you an overview; this tool gives you the complete picture. ## URL Requirements - The URL must be a valid HTML documentation webpage from the microsoft.com domain - Binary files (PDF, DOCX, images, etc.) are not supported ## Output Format markdown with headings, code blocks, tables, and links preserved.
    ConnectorNo auth
  • Search across the nTop knowledge base to find relevant information, code examples, API references, and guides. Use this tool when you need to answer questions about nTop, find specific documentation, understand how features work, or locate implementation details. The search returns contextual content with titles and direct links to the documentation pages. If you need the full content of a specific page, use the query_docs_filesystem tool to `head` or `cat` the page path (append `.mdx` to the path returned from search — e.g. a result at `/some/page` is read with `head -200 /some/page.mdx`).
    ConnectorNo auth