show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Crisp
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already disclose readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds the scope ('MCP platform and adapter'), but no additional behavioral details beyond that.
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 one short, front-loaded sentence containing no filler or redundant information. It fully serves its purpose without wasted words.
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 zero-parameter tool with strong annotations, the description is sufficiently complete. It does not explicitly describe the return format, but the intent is clear enough for version-information retrieval.
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 accepts zero parameters, so there is nothing semantically to clarify. The schema coverage is complete and the description adds no unnecessary or missing 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 uses a specific verb ('Show') and clearly identifies the resource: current MCP platform and adapter versions. This clearly distinguishes it from sibling tools like authenticate, marketplace, and report_bug.
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: call it when current version information is needed. However, it does not explicitly state when to prefer this tool over alternatives or any selection context beyond the 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
Disambiguation2/5
The set has major overlap: `marketplace` and `search_tools` both offer search/describe/invoke catalog actions, making it unclear which to call. `report_bug` is also called out as a capability inside `marketplace`, blurring whether that tool is the action or the top-level one.
Naming Consistency3/5
All names are lowercase with underscores, but they mix verb-oriented names (`authenticate`, `connect`, `report_bug`) with noun-oriented names (`marketplace`, `search_tools`) and no consistent verb_noun pattern. `show_version` and `toolkit_info` are similarly status-like but follow different naming styles.
Tool Count4/5
Seven tools is within a reasonable range and the count itself is not problematic. However, the `marketplace` tool is overloaded with many sub-capabilities and `search_tools` duplicates part of it, so the effective scope feels less clean than the raw count suggests.
Completeness4/5
The main workflows are covered: authentication, connection status, catalog search, account/toolkit state, and bug reporting. Missing pieces like an obvious way to uninstall/disconnect or list callable tools are hidden inside `marketplace`, but these are workable gaps rather than fatal ones.