show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Trabalho Forçado (Lista Suja)
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 the qualifier 'current', indicating that the tool reflects the runtime state of the platform and adapter. This provides useful context beyond simple 'show version' and is consistent with the non-destructive nature hinted by annotations.
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 sentence of 10 words that is front-loaded with the verb and object. It contains no filler, repetition, or unnecessary details, making it highly concise and well-structured.
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 tool's simplicity (no parameters, no output schema, comprehensive annotations), the description fully explains what the tool does. It is complete enough for an agent to select and invoke the tool correctly without ambiguity.
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 baseline of 4 applies. There are no input semantics to clarify; the description appropriately avoids irrelevant parameter details.
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 'Show the current MCP platform and adapter versions' uses a specific verb ('Show') and clearly identifies the resource (versions). It distinguishes itself from siblings like 'authenticate' or 'marketplace' by focusing solely on version information, making the purpose unmistakable.
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?
No explicit guidance is given on when to use this tool versus alternatives, such as 'toolkit_info'. However, the purpose strongly implies usage whenever version information is needed. Since it lacks explicit when-not-to-use or alternative references, it only meets the 'implied usage' standard.
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
Disambiguation4/5
Tools have distinct purposes: authentication, connection status, marketplace operations, bug reporting, version info, toolkit state, and a specific domain query. Some minor overlap exists between connect and toolkit_info (both report connection status), but generally an agent can choose correctly.
Naming Consistency2/5
Naming is inconsistent: some are bare verbs (authenticate, connect), some are verb_noun (report_bug, show_version), some are nouns (marketplace, toolkit_info), and one is Portuguese with the verb at the end (trabalho_forcado_consultar). There is no uniform pattern across the set.
Tool Count3/5
Seven tools is a reasonable number, but the server's name suggests a domain-specific scope (forced labor list), and six of the seven tools are generic platform utilities. The count feels imbalanced—too many meta-tools and too few domain tools relative to the apparent purpose.
Completeness2/5
The platform side is fairly complete (auth, status, marketplace, bug reporting, version, toolkit state), but the domain side is extremely thin: a single query tool for the dirty list, with no other operations like listing, batch checks, or historical data. For a server named after the domain, this is a significant gap.