A
license-
qualityD
maintenanceMCP server for documentation search that automatically indexes web documentation sites and provides semantic, full-text, or hybrid search capabilities.
8
MIT
docs
Server Details
Stimulsoft Reports & Dashboards docs MCP server. Semantic search for all platforms.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
MCP client
Glama
MCP server
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
100% free. Your data is private.
Tool Definition Quality
A4.4/5.0
Tool DescriptionsA
Average 4.7/5 across 2 of 2 tools scored.
Server CoherenceA
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.
Available Tools
2 toolssti_get_platformsAInspect
List every Stimulsoft product/platform that has indexed documentation available through this MCP server. Returns a JSON array of { id, name, description } objects covering the full Stimulsoft Reports & Dashboards product line (Reports.NET, Reports.WPF, Reports.AVALONIA, Reports.WEB for ASP.NET, Reports.BLAZOR, Reports.ANGULAR, Reports.REACT, Reports.JS, Reports.PHP, Reports.JAVA, Reports.PYTHON, Server API, etc.).
CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid platform value to pass into sti_search. The returned platform id values are the exact strings accepted by the platform parameter of sti_search.
This tool is cheap (no OpenAI call, no vector search) — call it freely whenever you are unsure about platform naming.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Tool Definition Quality
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. States it returns a JSON array of { id, name, description } objects and is 'cheap (no OpenAI call, no vector search)'. This implies read-only and safe operation. Lacks explicit mention of error handling or data freshness, but sufficient for a listing tool.
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-organized: first sentence states purpose, then details return format, followed by usage guidance. Slightly verbose but every sentence adds value. Front-loaded with key information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given no output schema and no annotations, description covers purpose, return structure, relationship to sibling tool, and behavioral traits (low cost). Lacks details on error handling or limits, but complete enough for a zero-parameter listing tool.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
No parameters exist; schema coverage is 100%. The description adds value by explaining that the returned platform IDs are the exact values accepted by sti_search, going beyond the empty 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?
Clearly states 'List every Stimulsoft product/platform that has indexed documentation available through this MCP server.' Specifies the return format and explicitly contrasts with the sibling tool sti_search by noting that returned IDs are needed for sti_search's platform parameter.
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?
Explicitly advises 'CALL THIS FIRST when the user's question is ambiguous about which Stimulsoft platform they are using, or when you need to pick a valid platform value to pass into sti_search.' Also encourages calling freely due to low cost, providing clear when-to and when-not-to guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
sti_searchAInspect
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.
ParametersJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum 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. | |
| query | Yes | The 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'. | |
| category | No | Optional. 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. | |
| platform | No | Optional. 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. |
Tool Definition Quality
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.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Servers
- Alicense-qualityDmaintenanceMCP server for RAG-based search over 1C Enterprise configuration documentation, enabling natural language queries to find objects like справочники, документы, and отчеты.MIT
- Alicense-qualityDmaintenanceMCP server for TeamDesk databases, enabling CRUD operations, search, and document generation via natural language.3MIT
- Alicense-qualityDmaintenanceEnterprise-grade document editing and management server that enables AI-powered operations on Microsoft Word DOCX files, including creating, editing, formatting, and exporting documents through both MCP protocol and RESTful API.3MIT