Skip to main content
Glama

docs

by com.stimulsoft

sti_search

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.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Default 5, maximum 20. Use 3–5 for focused lookups, 10–20 when exploring or when the first search was too narrow.
queryYesThe user's question or topic, in any language. Keep it close to the original wording — do not translate or over-summarize. Good examples: 'how to export report to PDF in Blazor', 'как показать StiViewer в WPF на весь экран', 'StiWebViewer show/hide toolbar buttons', 'connect StiReport to REST API JSON data source', 'StiBlazorViewer FullScreenMode'. Bad examples (too vague): 'reports', 'help', 'error'.
categoryNoOptional. Restrict the search to a documentation section: `faq` (frequently asked questions with code snippets), `manual` (Programming Manual), `api` (API Reference), `guide` (How-to guides). Omit to search all categories.
platformNoOptional. Restrict the search to a single Stimulsoft platform. Accepted values (case-sensitive): NET (WinForms / Reports.NET), WPF, AVALONIA, WEB (ASP.NET / ASP.NET Core / MVC), BLAZOR (Blazor Server / WebAssembly), ANGULAR, REACT, JS (vanilla HTML/JS), PHP, JAVA (Java SE / Jakarta EE), PYTHON, SERVER_API, GENERAL. If you are not 100% sure which id to use, either call `sti_get_platforms` first, or omit this field.

TDQS

A4.9/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description fully covers behavior: search strategy, handling low scores, reformulating queries, multiple focused searches. It also warns that training data is out of date and the tool should be used for up-to-date info.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with bold headers and clear sections. Though lengthy, every sentence serves a purpose. Slightly verbose but justified given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite no output schema, the description explains the return format (ranked JSON array with fields including content). It covers all necessary aspects: purpose, parameters, strategies, and output, making it self-contained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but the description adds significant value: examples of good/bad queries, limit usage (3-5 vs 10-20), category meanings, and platform values. This goes well beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it performs 'Authoritative semantic search over the official Stimulsoft Reports & Dashboards developer documentation'. It distinguishes itself from the sibling tool 'sti_get_platforms' by explaining when to use that tool for platform IDs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit when-to-use scenarios (e.g., any Stimulsoft-related query) and when-not-to-use (e.g., non-Stimulsoft topics). Also explains when to use the sibling tool and search strategies.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All docs toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation5/5

The two tools have entirely distinct purposes: one lists available platforms, the other performs semantic search. There is no overlap or confusion between them.

Naming Consistency5/5

Both tools follow a consistent 'sti_verb_noun' pattern (sti_get_platforms, sti_search), making the naming predictable and clear.

Tool Count3/5

With only 2 tools, the server covers the core search workflow but feels minimal. A few additional tools (e.g., to retrieve a specific document or list categories) would make it more robust.

Completeness3/5

The tools allow listing platforms and searching documentation, which covers basic needs. However, there is no way to browse documents by category or retrieve a specific section without searching, which may limit direct navigation.

Resources