show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
SINTEGRA: SE
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the specific scope of reporting 'platform and adapter versions' but does not disclose any additional behavior such as output format or network dependencies. This is adequate but not rich.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness5/5
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single sentence with no filler. Every word contributes meaning, identifying the exact information the tool returns.
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 the tool's simplicity, zero parameters, and strong annotations, the description is sufficient for an agent to select and invoke it. It could mention return format, but 'Show' strongly implies a readable version string. Overall, no critical information is missing.
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?
The tool has zero parameters, so parameter semantics are not applicable. The description correctly focuses on what the tool reports rather than on inputs, and the schema coverage is trivially complete.
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 uses a specific verb ('Show') with a clear resource ('the current MCP platform and adapter versions'). It accurately distinguishes this tool from siblings like toolkit_info and authenticate, which clearly serve different purposes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage when version information is needed, but there is no explicit guidance about when to use it versus alternatives. For a simple version-check tool, this is acceptable but not fully explicit.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.6/5.0
Disambiguation3/5
Most tools are distinct (authenticate, show_version, report_bug), but there is overlap: connect and toolkit_info both report connection status, and marketplace's list_tools overlaps with toolkit_info. The marketplace tool is a broad catch-all covering search, invoke, install, and billing, which could cause misselection.
Naming Consistency2/5
Naming is inconsistent: some tools are verbs (authenticate, connect, report_bug), some are nouns (marketplace, toolkit_info), and one is domain-specific (sintegra_se_consultar) with a different style. No clear verb_noun pattern across the set.
Tool Count4/5
Seven tools is a reasonable count for a platform-level server, though the inclusion of a single domain-specific tool (sintegra_se_consultar) alongside generic platform tools feels disproportionate given the server's name.
Completeness4/5
The platform surface is fairly complete: authentication, connection status, marketplace with search/invoke/install, feedback, version, and toolkit info. Minor gaps exist (e.g., no explicit credential management beyond authenticate, but marketplace actions cover most needs). For the specific SINTEGRA domain, only one query tool exists, but that may be intentional as this is primarily a platform server.