show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Similaridade de Identidade (Brasil)
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.5/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the tool's non-mutating behavior is established. The description adds context by specifying that it returns 'current' platform and adapter versions, which aligns with the read-only nature.
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, focused sentence that front-loads the verb and object. Every word earns its place, with no redundant detail or padding.
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 tool with no parameters, no output schema, and a trivial operation, the description fully captures the tool's purpose and scope. Nothing else is needed.
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 description need not explain any input semantics. The baseline of 4 applies as there is no additional burden for the description to compensate.
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' with a clear resource ('the current MCP platform and adapter versions'), leaving no ambiguity about the tool's function. It distinguishes itself from siblings like authenticate or marketplace by focusing solely on version information.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines4/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is for retrieving version details when needed. Context is clear and self-contained, with no exclusions or alternatives mentioned, which is acceptable given the simplicity of the operation.
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
A4.1/5.0
Disambiguation3/5
The core consultation tool is distinct, but authenticate and connect overlap somewhat around authentication/connection status, and marketplace is a sprawling tool covering many sub-actions (search, invoke, install, etc.) that overlaps with report_bug and toolkit_info. Detailed descriptions help, but boundaries remain fuzzy.
Naming Consistency2/5
Tool names mix single-word verbs (authenticate, connect), noun_verb (report_bug, show_version), noun_noun (toolkit_info), a marketplace noun, and a Portuguese domain name (similaridade_br_consultar). There is no consistent naming convention across the set.
Tool Count4/5
Seven tools is a reasonable size, but most tools are generic MCP platform utilities rather than serving the identity similarity purpose. The count itself is fine, though the scope feels a bit unfocused.
Completeness4/5
The primary operation of querying identity similarity is covered, along with authentication and connection status. Billing and marketplace operations are also present. Minor gaps exist, such as no explicit balance/credit check, but these are indirectly handled via marketplace links.