show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
SINTEGRA: GO
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/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, which fully cover the safety profile. The description adds that it shows 'current' versions, which is minor scoping context but does not disclose additional behavioral traits like return format or potential side effects.
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 that is front-loaded, direct, and free of filler. Every word contributes to defining the tool's purpose.
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?
For a zero-parameter, read-only, idempotent tool with rich annotations, the description fully covers the essential purpose. The absence of an output schema is not a gap because the description clearly states what information (platform and adapter versions) will be shown.
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 the schema is trivially complete. The description adds meaning by clarifying the exact kind of version information that will be returned, which is sufficient for a parameterless tool.
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 clear verb ('Show') and specifies the exact resource ('current MCP platform and adapter versions'), making the tool's purpose immediately obvious. It also distinguishes this from siblings like 'toolkit_info' by naming the specific version-related output scope.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool versus alternatives such as 'toolkit_info' or 'marketplace'. The description does not mention any context, exclusions, or prerequisites, leaving the agent to infer the appropriate usage scenario.
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
Disambiguation4/5
Most tools have distinct purposes: auth, connection status, marketplace, feedback, version, query, toolkit state. However, 'connect' and 'toolkit_info' both convey connection status, and 'marketplace' is a catch-all for many sub-operations, creating minor overlap.
Naming Consistency3/5
Names are inconsistent: some are generic verbs (authenticate, connect), some are nouns (marketplace, toolkit_info), and sintegra_go_consultar uses Portuguese. There's no uniform verb_noun pattern, though they're all snake_case and readable.
Tool Count4/5
With 7 tools, the count is reasonable, though the server seems to bundle platform utilities with a single domain-specific tool, making the scope slightly muddled. Each tool has a distinct function, so it's not overly heavy.
Completeness4/5
For a SINTEGRA GO server, only one domain tool exists, but the marketplace tool provides broad access to other MCPsWFilling gaps. Platform operations (auth, status, feedback, version, toolkit info) are covered, but the domain surface is thin.