show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
SINTEGRA: MS
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds value by specifying exactly what is shown (MCP platform and adapter versions), which goes beyond raw annotations. However, it does not describe the output format or any other behavioral details, but for a simple read-only tool this is sufficient.
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, concise sentence that fully communicates the action and scope. No wasted words; it is front-loaded and efficient.
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?
Given the simplicity of the tool (no parameters, no output schema, strong annotations), the description is complete. It tells the agent exactly what the tool does, and the annotations cover safety aspects. There are no gaps that need further explanation.
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, and schema description coverage is 100% (empty schema). Per the rubric, with 0 params the baseline is 4. The description adds no parameter details because there are none, so the baseline is appropriate.
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 shows the current MCP platform and adapter versions, using a specific verb ('Show') and resource ('versions'). It distinguishes from siblings like 'toolkit_info' by focusing specifically on versions, and the name reinforces the purpose.
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 does not explicitly mention when to use this tool versus alternatives or any exclusions. While the context is clear from the name and description, there is no guidance on when not to use it or how it differs from potentially overlapping tools like 'toolkit_info'.
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.8/5.0
Disambiguation4/5
Each tool serves a distinct purpose: authenticate handles login, connect reports status, marketplace is the central hub for searching and executing MCPs, report_bug sends feedback, show_version displays versions, sintegra_ms_consultar performs a specific data lookup, and toolkit_info summarizes the environment. The only potential overlap is between authenticate and connect, but they are clearly separated by actions (login vs. check status). The marketplace tool is broad but has a well-defined scope, so misselection is unlikely.
Naming Consistency3/5
Naming is mixed: some tools use verb_noun (show_version, toolkit_info), some are single verbs (authenticate, connect), and marketplace is a noun. Additionally, sintegra_ms_consultar includes a proper name and a Portuguese verb, deviating from the pattern. While all names are readable, the inconsistency is noticeable and could confuse agents expecting a uniform convention.
Tool Count4/5
Seven tools is a reasonable count for a platform that combines a marketplace, user management, and a specific data query. The count is not excessive and each tool seems necessary, though the marketplace tool bundles many sub-actions (search, describe, invoke, list, install, subscribe, etc.) into one surface, which might justify a higher count but still remains within a sensible range.
Completeness4/5
The platform covers core operations: authentication, connection status, marketplace discovery/execution, bug reporting, version info, and toolkit state. Minor gaps exist, such as a dedicated logout or token revocation function, but the marketplace tool includes billing and subscription management, so most needs are met. The SINTEGRA MS tool is a standalone query, which is complete for its purpose.