show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Óbito
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, so the burden is lower. The description adds valuable context by specifying that it reports platform and adapter versions, going beyond the bare annotation hints.
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, focused sentence communicates the tool's purpose without any filler. It is immediately understandable and appropriately sized.
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?
The tool is extremely simple, with no parameters and annotations covering its safety profile. The description fully specifies what it reports, and the absence of an output schema does not hinder understanding for a version check tool.
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?
With zero parameters and a schema that covers 100% of the (empty) property set, there is no parameter semantics to add. The baseline of 4 applies as the description cannot meaningfully compensate further.
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.' It clearly distinguishes from sibling tools like authenticate or marketplace, making its purpose unambiguous.
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 checking version information, providing clear context without explicit exclusions or alternative recommendations. Since siblings are unrelated, the usage context is sufficiently clear.
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
Disambiguation4/5
Most tools have clear, distinct purposes (marketplace, obito_consultar, report_bug, show_version, toolkit_info). The only ambiguity is between authenticate and connect, both of which deal with authentication and connection status, which could cause an agent to pick the wrong one.
Naming Consistency2/5
Naming styles are inconsistent: some tools use single verbs (authenticate, connect), some use snake_case verb_noun (obito_consultar, report_bug), and others use noun forms (marketplace, toolkit_info) or mixed (show_version). There is also a mix of English and Portuguese, further reducing predictability.
Tool Count4/5
7 tools is a reasonable count, falling within the typical 3-15 range. The count is appropriate, though the server mixes a single domain-specific tool with several platform-level utilities, which makes the scope slightly uneven but not excessive.
Completeness2/5
The server is named 'Óbito' and the core purpose appears to be death-status consultation via obito_consultar, but the tool surface includes only that one domain operation. There are no supporting tools like query history, batch lookup, or results reporting, so the domain coverage is notably shallow. The platform tools are broad, but they don't compensate for the limited domain-specific functionality.