show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Conta Simples
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?
The description is consistent with annotations (readOnlyHint, idempotentHint, destructiveHint) and adds the context of returning 'current' versions. No contradictions.
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?
One sentence that is front-loaded and contains all necessary information with no wasted words.
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 version information tool with no output schema, the description fully explains what it returns. No additional details are 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 schema coverage is 100% by default. The description does not need to add parameter information; baseline score is appropriate.
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 identifies the resource clearly as 'MCP platform and adapter versions'. It is unique among sibling tools, which focus on accounts, authentication, etc.
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 when to use (to check current versions) but does not explicitly state when not to use or mention alternatives. However, for a simple informational tool, this is sufficient.
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.5/5.0
Disambiguation4/5
Almost all tools have clear purposes, especially with the contasimples_ prefix. Some overlap between statement and summary, but descriptions differentiate well. The general tools (marketplace, report_bug, etc.) are completely different from the financial ones, which reduces potential confusion.
Naming Consistency3/5
The domain tools follow a consistent verb_noun pattern (e.g., contasimples_card_write_block). However, the inclusion of general tools like authenticate, connect, marketplace breaks the pattern. This inconsistency lowers the score.
Tool Count4/5
With 24 tools covering authentication, financial operations, and platform utilities, the number is reasonable for a moderately complex MCP server. It doesn't feel excessive or too thin.
Completeness3/5
The toolset covers key financial operations (balance, bills, cards, statements, summary) and some mutations (block/unblock, create invite, delete user). However, missing CRUD for several entities (e.g., no update user, no create card, no delete invite) leaves gaps. The presence of platform utilities adds breadth but not depth.