show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
SINTEGRA: PB
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=true and idempotentHint=true. The description adds useful context by specifying that it shows both platform and adapter versions, clarifying the exact scope of the read operation.
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?
A single, front-loaded sentence with no wasted words. It states the action and the object clearly and completely.
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 version tool with no output schema, the description is fully adequate. It tells the agent exactly what information will be returned without unnecessary detail.
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, which earns the baseline 4. The description correctly implies no inputs are needed, and there is nothing else to compensate for.
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') and names a clear resource ('current MCP platform and adapter versions'). It distinguishes itself from siblings like toolkit_info by focusing specifically on version information.
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 use when the user needs version details, but it does not explicitly state when to use this tool versus alternatives. Given the simplicity of the tool, no exclusions are stated, but this still falls short of explicit guidance.
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
Disambiguation2/5
The marketplace tool is a god-object combining discovery, execution, installation, billing, and a prompt library under one name, making intent selection ambiguous. At the same time, authenticate, connect, show_version, and toolkit_info all blur together around 'platform state,' forcing an agent to guess which one applies. Only sintegra_pb_consultar is unambiguous in purpose.
Naming Consistency2/5
Naming conventions are mixed across bare verbs (authenticate, connect), a bare noun (marketplace), snake_case verb_noun (report_bug, show_version), noun_noun (toolkit_info), and Portuguese noun-verb (sintegra_pb_consultar). While the Portuguese is thematically appropriate for a Brazilian service, mixing two languages and three structural patterns in a 7-tool surface shows no governing convention.
Tool Count3/5
At 7 tools, the raw count sits comfortably in the ideal range, but composition is lopsided: 6 of 7 tools are generic platform plumbing (auth, connectivity, version, bug reports, toolkit state) while only one serves the SINTEGRA: PB domain. The marketplace tool alone likely encapsulates 5-8 distinct operations that would be separate tools in a well-factored server.
Completeness2/5
The actual SINTEGRA domain receives a single tool with no supporting operations: no credit-balance check for the prepaid model, no query history, no receipt, and no result-formatting variants. The abundant platform tooling (install, subscribe, publish prompts) addresses the marketplace ecosystem but does nothing to close the gaps in the one service the server claims to deliver.