show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
MPT (Ministério Público do Trabalho)
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?
Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds that it reports 'current' versions, but does not elaborate on return format or whether live queries occur. Value added beyond annotations is minimal.
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?
Single sentence, highly concise, no filler. It immediately states the action and target resource.
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?
For a simple version query, the description adequately covers purpose and scope. However, with no output schema, it could mention the return structure (e.g., separate values for platform and adapter). Still, the simplicity means this is near-complete.
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?
Tool has zero parameters, so baseline is 4. Description does not need to compensate for schema gaps since there are none.
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 shows current MCP platform and adapter versions, using a specific verb and resource. It distinguishes itself from siblings like toolkit_info by being version-specific.
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?
No guidance is provided on when to use this tool versus alternatives. The description is purely definitional and does not mention any context, prerequisites, or exclusions.
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
Disambiguation3/5
The marketplace tool bundles many sub-actions (search, describe, invoke, install, prompts, etc.) that overlap with report_bug, connect, and toolkit_info, making it unclear which tool to choose for a given task. However, mpt_consultar is clearly distinct, and the core tools are mostly separable.
Naming Consistency2/5
Tool names mix single verbs (authenticate, connect), nouns (marketplace, toolkit_info), Portuguese verbs (mpt_consultar), and snake_case verb_noun patterns (report_bug, show_version). There is no consistent naming convention, which reduces predictability.
Tool Count4/5
Seven tools is a reasonable count for a platform server covering authentication, connection status, marketplace access, bug reporting, versioning, and toolkit state. The broad scope justifies the number, though one tool (marketplace) carries a disproportionate amount of functionality.
Completeness4/5
The platform lifecycle is well-covered: authentication, connection checks, marketplace exploration/invocation/installation, billing, bug reporting, and version/info. The mpt_consultar tool addresses the specific MPT domain query. Minor gaps exist, such as no dedicated credential management beyond authenticate, but core workflows are not dead-ended.