Bryntum Suite
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
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.
Average 3.7/5 across 1 of 1 tools scored.
Only one tool exists, so there is no possibility of overlapping purposes. Every query is directed to the same search action.
The single tool name follows a clear verb_noun pattern (search_bryntum_docs), which is consistent and predictable.
A single search tool feels thin for a documentation server covering multiple Bryntum products, but it could be acceptable for a narrow search-only use case.
The tool provides search but lacks a direct document retrieval or listing capability, so agents cannot fetch full page content or browse the documentation structure.
search_bryntum_docsAInspectSearch Bryntum product documentation for technical information. Use this to find API references, configuration options, examples, and best practices for Bryntum products like Scheduler, Scheduler Pro, Gantt, Calendar, Grid, and TaskBoard. You must provide a version of the libray you are using. It can usally be found in package.json. If you can t fine it, use latest.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of results to return (default: 10, max: 100) | |
| query | Yes | Natural language search query describing what you want to find | |
| product | No | Filter by specific Bryntum product (e.g., scheduler, schedulerpro, gantt, calendar, grid, taskboard) | |
| version | No | Filter by documentation version. Use 'latest' for most recent version. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden. It discloses a behavioral requirement (version must be provided) that goes beyond the schema, but it does not explain return format, error handling, or what happens if an invalid version is given. The typo-ridden version sentence adds ambiguity, leaving some behavioral aspects unclear.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is reasonably sized and front-loaded with purpose, but it contains several typos ('libray', 'usally', 'can t fine') and a clunky version instruction that could be condensed. The message is clear but not polished, and each sentence does not earn its place efficiently.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple search tool with well-documented parameters, the description provides adequate context for use, but it omits details about output format and the apparent contradiction between 'must provide a version' and the schema marking version as optional. This makes the description merely sufficient, not complete.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so baseline is 3. The description adds minor value by suggesting the version can be found in package.json, but it redundantly reiterates the schema's 'use latest' tip. Overall, it does not significantly enrich the parameter meanings beyond what the schema already provides.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description explicitly states the tool 'Search Bryntum product documentation for technical information' and lists concrete use cases (API references, configuration options, examples, best practices) and product names. This clearly identifies the tool's purpose and resource, making it distinguishable even without siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description tells the agent when to use it ('Use this to find...') and provides a critical usage instruction: a version must be provided, with guidance on locating it in package.json and falling back to 'latest'. It does not mention alternatives because none exist, but the guidance is practical and actionable.
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.
No comments yet. Be the first to start the discussion!
