show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Agger
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which cover the safety profile. The description adds no extra context beyond confirming it shows information, but it does not contradict annotations, so a baseline score of 3 is appropriate.
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, succinct sentence that front-loads the verb and resource with zero wasted words. It is perfectly concise for the tool's trivial purpose.
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 simple version query with no parameters, no output schema, and thorough annotations, the description fully satisfies the need. It clearly states what the tool does without requiring additional behavioral details.
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, and the schema reflects that with an empty properties object. Per rubric, 0 parameters earns a baseline score of 4. The description adds no parameter info because none exist, which is sufficient.
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 clearly states the verb 'Show' and the resource 'current MCP platform and adapter versions', making the tool's purpose unambiguous. It is distinct from sibling tools which involve listing accounts, authentication, connecting, marketplace, reporting bugs, or getting toolkit info.
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 usage (to view version info) and there are no alternative tools for this specific purpose, so no explicit when-not guidance is needed. The simplicity of the tool makes the intended context 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.8/5.0
Disambiguation5/5
Each tool targets a distinct function: CEP lookup, quote validation, dashboard stats, account listing, business listing, insurer listing, and separate platform utilities for auth, connectivity, marketplace, bug reports, version, and toolkit state. No two tools overlap in purpose, so an agent can clearly differentiate them.
Naming Consistency2/5
Tool names mix conventions: some are bare nouns (agger_cep, agger_negocios, marketplace), some use verb_noun (agger_list_accounts, report_bug, show_version), one is noun_verb (agger_cotacao_validar), and several are generic single verbs (authenticate, connect). This inconsistency makes the naming pattern unpredictable and harder to infer.
Tool Count5/5
The 12-tool set is well-scoped: 6 domain-specific Agger tools cover the core insurance broker workflows, and 6 generic platform tools handle authentication, connectivity, marketplace operations, and diagnostics. Each tool earns its place without unnecessary bloat.
Completeness3/5
The domain coverage is partial: the server supports listing businesses, validating quotes, and viewing insurers, but lacks create/update/delete operations for quotes or detailed single-item views. Some gaps exist (e.g., no create quote, no get_business_detail), but agents can work around them by using the list and validation tools, and the platform utilities address meta-level needs.