show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Atualização Monetária
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.8/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, describing the safety profile. The description adds only the phrase 'current', which slightly clarifies freshness but does not meaningfully expand on behavior beyond what annotations provide.
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 concise sentence with no redundant filler. The gerund 'Show' front-loads the action and the resource is specified with just enough detail.
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?
Given the trivial parameter surface, rich annotations, and no output schema, the description sufficiently communicates what the tool returns: current MCP platform and adapter versions. It does not describe output formatting, but for a version-info tool this is a minor gap.
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 schema provides complete coverage and there is nothing for the description to clarify. Baseline 4 is appropriate because the description is not required to explain parameter meaning.
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 states a specific verb ('Show') and a clear resource ('MCP platform and adapter versions'), making the tool's purpose immediately understandable. It is also distinct from the sibling tools, none of which target 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 Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no guidance about when to use this tool versus alternatives such as toolkit_info or connect. For a simple zero-parameter tool this is functional, but the absence of any usage context keeps it at the 'no guidance' level.
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.6/5.0
Disambiguation4/5
Each calculo_* tool targets a distinct legal/financial area (rent, alimony, FGTS, criminal sentencing, etc.), and their descriptions cite specific statutes that make the purpose clear. The only mild ambiguity is that calculo_atualizar and calculo_indice both handle generic monetary correction, while some INSS/FGTS tools share 'refund plus correction' semantics, but the specialized names avoid serious confusion.
Naming Consistency3/5
The 16 domain tools follow a consistent 'calculo_<topic>' snake_case pattern, but calculo_atualizar uses a verb where the rest use nouns. The six platform tools break the pattern entirely with short English names (authenticate, connect, marketplace, report_bug, show_version, toolkit_info), resulting in two readable but distinct naming conventions.
Tool Count3/5
At 22 tools, the set is in the heavy range, and while the 16 legal calculators each justify their place, the six unrelated MCP platform utilities bloat the count for a server named 'Atualização Monetária'. The breadth of the legal calculators makes this borderline rather than excessive, but the overall scope is less focused than a well-scoped 10-15 tool server.
Completeness4/5
The toolkit covers a remarkably wide set of Brazilian legal calculations: monetary correction, index factors, alimony, labor severance, FGTS, INSS refunds, bank contract revisions, criminal sentencing, prison progression, family division, retirement benefits, and contribution time. Minor gaps exist, such as no standalone general-interest calculator and no OCR for FGTS statements yet, but agents can work around these with the generic tools.