show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Organizze
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering safety. The description adds useful context about what is being reported (platform vs adapter versions), which goes slightly beyond the annotations.
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, well-formed sentence that states the tool's purpose without any filler. It is front-loaded and every word contributes meaning.
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 zero-parameter, read-only version inspection tool, the description plus annotations fully cover what an agent needs. No output schema is present, but the tool is trivial and the description sufficiently indicates what information will be returned.
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 parameter semantics are not a concern. The description does not need to explain any parameters, and the schema coverage is already complete.
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 a clear resource ('current MCP platform and adapter versions'). This distinguishes it from all sibling tools, including the more general toolkit_info, because it targets version information specifically.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
The use case is implied: call this when you need to know the MCP platform or adapter versions. It does not explicitly mention alternatives or exclusions, but the tool is simple enough that the implied purpose is fairly 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
B3.1/5.0
Disambiguation3/5
Most tools target distinct resource+action pairs, but the reporting/query side is crowded: get_balances, transactions_list_results, get_financial_summary, get_monthly_overview, and the category/tag reports overlap heavily. Long descriptions disambiguate bases and use cases, but an agent must read carefully to avoid picking the wrong report or list variant.
Naming Consistency4/5
Organizze tools overwhelmingly follow a consistent organizze_<verb>_<noun> snake_case pattern with create_, list_, get_, update_, and delete_ prefixes. Deviations like transactions_list_results, the mass_* versus update_transactions_* bulk variants, and unprefixed platform tools keep it from being perfect.
Tool Count1/5
68 tools is far beyond the practical agent surface and includes many near-variant list/report/mass tools plus six unrelated platform-level tools. Even though the finance domain is broad, this count creates an extreme mismatch for efficient tool selection.
Completeness3/5
The core finance lifecycle is well covered: accounts, cards, categories, budgets, transactions, invoices, transfers, and reports all have substantial CRUD or equivalent support. However, some referenced operations are missing entirely, such as delete_recurrence, clear_latest_imports, and remove_from_latest_imports, and transfers/recurrences lack full lifecycle coverage.