Skip to main content
Glama
754,120 tools. Updated 2026-11-07 00:13

"Retrieve the latest documentation of libraries in word embeddings form for LLMs" matching MCP tools:

  • Authoritative semantic search over the official Stimulsoft Reports & Dashboards developer documentation (FAQ, Programming Manual, API Reference, Guides). Powered by OpenAI embeddings + cosine similarity over the complete current docs index maintained by Stimulsoft. Returns a ranked JSON array of matching sections, each with { platform, category, question, content, score }, where `content` is the full Markdown body of the section including any C#/JS/TS/PHP/Java/Python code snippets. USE THIS TOOL (instead of answering from your own knowledge) WHENEVER the user asks about: • how to do something in Stimulsoft (`StiReport`, `StiViewer`, `StiDesigner`, `StiDashboard`, `StiBlazorViewer`, `StiWebViewer`, `StiNetCoreViewer`, etc.); • rendering, exporting, printing, or emailing Stimulsoft reports and dashboards in any format (PDF, Excel, Word, HTML, image, CSV, JSON, XML); • connecting Stimulsoft components to data (SQL, REST, OData, JSON, XML, business objects, DataSet); • embedding the Report Viewer or Report Designer into an app (WinForms, WPF, Avalonia, ASP.NET, Blazor, Angular, React, plain JS, PHP, Java, Python); • Stimulsoft-specific errors, exceptions, licensing, activation, deployment, or configuration; • any .mrt / .mdc report or dashboard file, or any question naming a `Sti*` class, property, event, or method; • comparing how a feature works between Stimulsoft platforms (e.g. "WinForms vs Blazor viewer options"). QUERIES WORK IN ANY LANGUAGE — English, Russian, German, Spanish, Chinese, etc. Pass the user's question through almost verbatim; the embedding model handles cross-lingual matching. Do NOT translate queries yourself. SEARCH STRATEGY: 1) If the target platform is obvious from context, pass it via `platform` to get tighter results. 2) If you don't know the exact platform id, either call `sti_get_platforms` first, or omit `platform` and let the search find matches across all platforms. 3) If the first search returns low scores (<0.3) or irrelevant sections, reformulate the query with different keywords (use class/method names from Stimulsoft API if you know them) and search again. 4) Prefer multiple focused searches over one broad search. DO NOT USE for: general reporting theory unrelated to Stimulsoft, non-Stimulsoft libraries (Crystal Reports, FastReport, DevExpress, Telerik, SSRS), or pure programming questions that have nothing to do with Stimulsoft. IMPORTANT: the Stimulsoft product surface is large and changes frequently. Your training data is almost certainly out of date. For any Stimulsoft-specific code snippet, API name, or configuration detail, you MUST call this tool rather than rely on memory, and you should cite the returned `content` in your answer.
    ConnectorNo auth
  • Authoritative semantic search over the official Stimulsoft Reports & Dashboards developer documentation (FAQ, Programming Manual, API Reference, Guides). Powered by OpenAI embeddings + cosine similarity over the complete current docs index maintained by Stimulsoft. Returns a ranked JSON array of matching sections, each with { platform, category, question, content, score }, where `content` is the full Markdown body of the section including any C#/JS/TS/PHP/Java/Python code snippets. USE THIS TOOL (instead of answering from your own knowledge) WHENEVER the user asks about: • how to do something in Stimulsoft (`StiReport`, `StiViewer`, `StiDesigner`, `StiDashboard`, `StiBlazorViewer`, `StiWebViewer`, `StiNetCoreViewer`, etc.); • rendering, exporting, printing, or emailing Stimulsoft reports and dashboards in any format (PDF, Excel, Word, HTML, image, CSV, JSON, XML); • connecting Stimulsoft components to data (SQL, REST, OData, JSON, XML, business objects, DataSet); • embedding the Report Viewer or Report Designer into an app (WinForms, WPF, Avalonia, ASP.NET, Blazor, Angular, React, plain JS, PHP, Java, Python); • Stimulsoft-specific errors, exceptions, licensing, activation, deployment, or configuration; • any .mrt / .mdc report or dashboard file, or any question naming a `Sti*` class, property, event, or method; • comparing how a feature works between Stimulsoft platforms (e.g. "WinForms vs Blazor viewer options"). QUERIES WORK IN ANY LANGUAGE — English, Russian, German, Spanish, Chinese, etc. Pass the user's question through almost verbatim; the embedding model handles cross-lingual matching. Do NOT translate queries yourself. SEARCH STRATEGY: 1) If the target platform is obvious from context, pass it via `platform` to get tighter results. 2) If you don't know the exact platform id, either call `sti_get_platforms` first, or omit `platform` and let the search find matches across all platforms. 3) If the first search returns low scores (<0.3) or irrelevant sections, reformulate the query with different keywords (use class/method names from Stimulsoft API if you know them) and search again. 4) Prefer multiple focused searches over one broad search. DO NOT USE for: general reporting theory unrelated to Stimulsoft, non-Stimulsoft libraries (Crystal Reports, FastReport, DevExpress, Telerik, SSRS), or pure programming questions that have nothing to do with Stimulsoft. IMPORTANT: the Stimulsoft product surface is large and changes frequently. Your training data is almost certainly out of date. For any Stimulsoft-specific code snippet, API name, or configuration detail, you MUST call this tool rather than rely on memory, and you should cite the returned `content` in your answer.
    ConnectorNo auth
  • Insert one sync marker on a clip's transcript. Use this when: - The user is explicit about WHERE the camera should pause / cut (e.g. "sync the word 'submit' to 4.2s of the demo"). - `auto_sync` ran but missed a step you care about. How matching works: - `word`: case-insensitive, punctuation-stripped. The first match in the transcript is used unless `occurrence > 1`. - `occurrence`: 1-indexed — pass 2 to target the SECOND time that word appears, 3 for the third, etc. Required when the word repeats. - `timestamp_seconds`: clip-relative seconds. When the clip has run TTS already (`generated_timestamps` present), the server inverse-maps this to original-recording seconds automatically. Constraints: the clip MUST be a video clip with a source recording (otherwise the frame thumbnail can't be extracted). The transcript must already contain the word — if not, you'll get `word_not_found` with a 200-char excerpt of the transcript to help you retry.
    ConnectorNo auth
  • Replaces a submission's entire data object with the values provided in data. This is a full overwrite, not a merge — any existing field not included in data will be cleared to empty. Keys in data must match the field IDs from the Data Template (Form) schema (via wdf_data_templates_get_schema_and_sample_submissions), not display labels — an unrecognized key may be silently dropped rather than raising an error. Before calling this tool, first call wdf_data_templates_submissions_get, wdf_data_templates_submissions_search or wdf_data_templates_submissions_list_recent to retrieve the current field values, then include the complete set of fields in data — the ones you're changing plus every field you want to keep.
    Connector
    Destructive
    No auth
  • Use this when the user supplies up to 10 exact CardDeals product IDs or brand slugs to compare in one call. Product IDs use the form brand:starbucks. Do not use it for fuzzy discovery; use search_gift_card_deals instead. Unknown IDs are returned in not_found instead of being guessed.
    ConnectorNo auth
  • Read and edit the workspace pronunciation dictionary (Settings → Team → Pronunciation Dictionary). Use it whenever the user asks how a word, name or acronym is said. Do NOT respell the word in the voiceover script instead: the respelling shows in the script and captions, and every new video needs the fix again. An entry is WORKSPACE-WIDE: it changes the word in every video in this workspace; tell the user when you add or change one. It applies when speech is generated, so regenerate (voiceover_batch generate_speech) the clips that say the word. action: • list — entries for `language` ("" for all): {entries: [{word, spelling, ipa, language, case_sensitive}], count} • set — add or change `word`'s entry with exactly one of `spelling` (a sound-alike respelling, works on every voice; prefer it) or `ipa` (IPA phonemes, English ElevenLabs voices only, ignored on clips with [audio tags]). An existing entry is not overwritten: you get error "entry_exists" with `current`; show the user both, confirm, then call again with replace: true. • remove — delete `word`'s entry in `language` (exact spelling and casing) • to_ipa — convert `text` (e.g. a respelling) to IPA, to check an ipa entry before setting it Editing needs an editor or admin role and a plan with the dictionary; a refusal says which: tell the user, don't retry.
    Connector
    Destructive
    No auth

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server for indexing and searching local text files using late-interaction retrieval (ColBERT-style MaxSim), enabling token-level relevance matching.
    2
    MIT

Matching MCP Connectors

  • 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
  • Returns instructions for migrating to PropelAuth in a frontend framework such as React, JavaScript, TypeScript, or when using Next.js for just the frontend (e.g. client-side rendered). Guidance includes migrating from several auth providers, such as Clerk or Auth0. Each guidance will include documentation from the auth provider and PropelAuth. It is important to follow the instructions carefully to ensure a successful integration. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc. CRITICAL: If the current implementation uses a traditional OAuth/OIDC flow (e.g., via express-openid-connect, passport-auth0, or similar backend-managed session libraries), you MUST select 'OAuth' as the framework, regardless of the frontend library (React/Vue/etc.). Only select 'React' or 'Javascript' if the current implementation uses a frontend-only SDK (like @auth0/auth0-react) or if using fullstack Next.js.
    ConnectorNo auth
  • Retrieve a Lemma schema by its ID via GET /v1/schemas/{id}. A schema declares how documents of a given type are interpreted and normalized. Returns SchemaMeta { id, description? } with additionalProperties open — implementations commonly include a `normalize` artifact (WASM that maps raw documents to canonical form) and its content hash. Use this when you need to interpret attribute keys returned by lemma_query_verified_attributes.
    ConnectorNo auth
  • Use this when the user has indicated interest in being followed up with — even before formal checkout. Capture is non-binding. **REQUIRED CONTACT FIELDS**: contact_name, contact_phone, best_consult_time. Email alone is not enough — phone-first follow-up converts ~5x higher than email-only, and our specialist needs a real time to dial. ASK FOR ALL THREE explicitly. **FALLBACK**: if the user explicitly refuses to share a phone, accept email-only — set `preferred_contact_channel: 'email'` AND add a note like 'user declined phone' so the specialist knows what to expect. Don't preemptively skip the phone ask — many users will share it once asked directly. **Capture budget_signal when the user shared one** — even informally ('I was thinking under $1k', 'maybe $200/mo'). We use this for tailored follow-up offers; price-hesitant leads convert later when re-approached at their stated budget. Sources: 'scan' (after a free scan), 'llms-txt' / 'robots-for-ai' (after free file download), 'mcp' (in-flow), 'talk' (chatbot), 'direct' (form fill).
    ConnectorNo auth
  • Complete-or-fail concordance: every words row in corpus whose lemma, dStrong, or (with by="surface") exact inflected surface form matches query. Route lemma/Strong's-number/surface-word lookups here, never by writing SQL or guessing occurrences from memory. This deployment caps one concordance result at 2000 occurrences and refuses anything broader, reporting the exact match count in the error. Call count first when a query might be broad - count is never capped.
    ConnectorNo auth
  • Retrieve the full content of a specific Costory documentation page by its public docs URL or page path. Use this after search_documentation returns results. Response starts with `Url: https://docs.costory.io/...`. When citing this page in chat, use that exact `Url:` as the markdown href — do not convert to a relative app path. EXAMPLE: "Show me the full page about cost explorer" → { page: "https://docs.costory.io/features/cost-explorer" }
    ConnectorOAuth
  • Creates a new submission for a specific Data Template (Form). Use this tool after obtaining the Data Template (Form) schema (via wdf_data_templates_get_schema_and_sample_submissions) and collecting all required information from the user. Keys in data must match the field IDs from the Data Template (Form) schema, not display labels — an unrecognized key may be silently dropped rather than raising an error. Provide all fields marked as required in the Data Template (Form) schema; omitted optional fields are simply left blank on the new submission.
    ConnectorNo auth
  • Get one merged, time-ordered feed of SEC insider activity for a company: Form 4 events, Schedule 13D/13G stake filings, and Form 144 sale notices, distinguished by the source_form field (form4 | sc13 | form144). The limit applies after merging, so companies with heavy Form 4 activity can crowd out 13D/G and 144 rows - use the dedicated tools for those. Unknown tickers fail with an error (404). Data delayed 24 hours (known_at); no price-derived fields.
    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
  • WHAT: Pointer to one legal HTML page. REQUIRED doc enum. Unknown doc → ok=false unknown_doc hint=/impressum. RETURNS doc + canonicalUrl. For full text call get_ai_page({path:'/'+doc}) or get_discovery(which=llms-urheberrecht) for the copyright corpus. German legal text is binding; /llms-copyright.txt is EN courtesy.
    ConnectorNo auth
  • Get the oldest baseline test snapshot for a single URL, including expired tests. For pre-computed baseline-vs-latest deltas without fetching full snapshots, use gvt_get_score_trend instead; for baselines across many URLs in one call, use gvt_list_baselines. Use with gvt_get_latest to compare baseline vs current when you need the full snapshot detail on both ends. The url must be passed exactly as the test was run — matching is exact string equality (scheme, host, path, trailing slash), not nearest-match. When unsure of the recorded form, discover it with gvt_list_tests first.
    ConnectorOAuth
  • Get the oldest baseline test snapshot for a single URL, including expired tests. For pre-computed baseline-vs-latest deltas without fetching full snapshots, use gvt_get_score_trend instead; for baselines across many URLs in one call, use gvt_list_baselines. Use with gvt_get_latest to compare baseline vs current when you need the full snapshot detail on both ends. The url must be passed exactly as the test was run — matching is exact string equality (scheme, host, path, trailing slash), not nearest-match. When unsure of the recorded form, discover it with gvt_list_tests first.
    ConnectorNo auth
  • Draft yes/no answers to attributes from my_attribute_options. Each is a factual claim about the business, so only draft answers the owner has confirmed in this conversation. Creates a DRAFT only — nothing on Google changes. Show the owner the draft this returns, word for word, and publish it with publish_change only after they say yes.
    ConnectorNo auth
  • Draft a public reply to one review, using its id from my_reviews. Replaces any existing reply. Two or three sentences in the owner's voice; never offer discounts, argue, or share personal details. Creates a DRAFT only — nothing on Google changes. Show the owner the draft this returns, word for word, and publish it with publish_change only after they say yes.
    ConnectorNo auth
  • Draft deleting one photo from the listing, using its id from my_photos. This one cannot be undone. Creates a DRAFT only — nothing on Google changes. Show the owner the draft this returns, word for word, and publish it with publish_change only after they say yes.
    ConnectorNo auth