show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
CVM (Valores Mobiliários)
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior2/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and idempotentHint=true, so the description adds minimal behavioral context. It simply says 'show,' which adds little beyond the annotations. There is no mention of response format, potential side effects, or any additional behavioral nuances.
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 that is front-loaded with the verb and key information. It contains no fluff and effectively communicates 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 simple no-parameter tool with strong safety annotations, the description is sufficiently complete. It specifies exactly what versions are shown (platform and adapter), which is adequate given the absence of an output schema.
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 is 4. The description correctly implies there is nothing to configure, and the schema confirms 100% coverage. No additional parameter explanation needed.
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 the specific verb 'show' and identifies the resource as 'current MCP platform and adapter versions.' This clearly distinguishes it from sibling tools like authenticate or connect, which serve different purposes.
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 usage for checking version information, but provides no explicit when-to-use guidance or mention of alternatives. No exclusions are stated, but the context of sibling tools makes the primary use case fairly obvious.
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.9/5.0
Disambiguation3/5
Most tools have clear, distinct purposes (authenticate, cvm_consultar, show_version), but connect and toolkit_info overlap in reporting connection status, and marketplace is a catch-all with many sub-actions (search, describe, invoke, install, list_tools, subscribe, etc.) that could be confused with separate tools like report_bug. Descriptions help, but boundaries are not always crisp.
Naming Consistency2/5
Tool names follow no consistent pattern: some are verbs (authenticate, connect, report_bug, show_version), some are nouns (marketplace, toolkit_info), and one uses snake_case with a Portuguese verb (cvm_consultar). Mixed conventions and unclear verb/noun styles make the set feel inconsistent.
Tool Count4/5
With 7 tools, the count is reasonable and not bloated. However, marketplace is an extremely large tool packing many capabilities, effectively expanding the surface. Still, the overall number is appropriate for a platform server that mixes marketplace functionality with a single domain query.
Completeness4/5
The server covers authentication, connection status, marketplace search/run/install/billing, bug reporting, version info, and toolkit state. Minor gaps exist (e.g., no explicit logout or account/profile management), but for its apparent purpose, the surface is largely complete and workable.