show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
MPF: Amazônia Protege
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description is consistent with the annotations (readOnly, idempotent, non-destructive) but adds little beyond them. It says 'current' implying live data, but does not elaborate on side effects (though none are implied).
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, clear sentence with no unnecessary words or fluff. It is appropriately sized for the tool's simplicity.
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?
The description explains what the tool returns (versions of MCP platform and adapter), which is sufficient for a simple read-only operation. It does not specify the format, but that is acceptable given the lack of an output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, so the schema fully covers this aspect. The description adds no extra parameter-related information, which is fine given the absence of parameters.
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 the tool's function: showing current MCP platform and adapter versions. It is specific and distinguishes itself from sibling tools like authenticate and connect.
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 state when to use this tool versus alternatives, but as a simple version-check tool, its purpose is self-evident. Lacks explicit guidance on when to invoke it (e.g., for debugging or compatibility checks).
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.7/5.0
Disambiguation3/5
Tools like authenticate, connect, report_bug, and show_version have distinct purposes. However, the 'marketplace' tool is a monolithic mega-tool that bundles search, describe, invoke, install, subscribe, cancel, and prompt-library operations, making it ambiguous which sub-action is intended. The domain-specific 'mpf_amazonia_protege_consultar' also sits awkwardly alongside generic platform tools.
Naming Consistency2/5
Names are inconsistent: some are single verbs (authenticate, connect), some are nouns (marketplace, toolkit_info), and one uses long snake_case (mpf_amazonia_protege_consultar). There is no coherent naming convention across the set, mixing verb-first, noun-first, and domain-specific styles.
Tool Count4/5
Seven tools is a reasonable number for a platform utility server. The count is not excessive, but the 'marketplace' tool absorbs many responsibilities, which skews the effective scope. A few generic tools (report_bug, show_version) are expected in such a platform.
Completeness3/5
The server covers authentication, connectivity, marketplace operations (search, invoke, install), bug reporting, versioning, and toolkit status. However, the marketplace tool's monolithic design hides sub-operations, and the domain-specific query tool (mpf_amazonia_protege_consultar) suggests a data source but only exposes one operation. Missing explicit logout or disconnect operations.