show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
DAP Pronaf PF
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4/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, covering the safety profile. The description adds that it shows platform and adapter versions, but does not detail output format or potential error behavior, nor is it necessary given 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?
The description is a single sentence, front-loaded with the verb and focus, with no unnecessary words. It is concise and well-structured.
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?
The tool is very simple, annotations are strong, and there is no output schema. The description states the core function adequately, though it does not explicitly mention return format; for a version check, this is sufficiently complete.
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 schema has 0 parameters, so there is no need for parameter documentation. Baseline for 0 params is 4, and the description does not need to compensate.
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 and resource: 'Show the current MCP platform and adapter versions.' It clearly distinguishes from siblings like authenticate/connect, which are about actions, not version info.
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?
No explicit when-to-use or when-not-to-use guidance is given, nor are alternatives mentioned. The purpose is self-evident, implying use when version information is needed, but the description does not explicitly differentiate from sibling tools.
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
Disambiguation3/5
Most tools have distinct purposes, but authenticate and connect both relate to authentication and connection status, which could cause confusion. Marketplace is a catch-all for many sub-functions, making it unclear when to use it versus other tools.
Naming Consistency2/5
Tool names are inconsistent: some are English verbs (authenticate, connect), some are nouns (marketplace, toolkit_info), and one is a Portuguese snake_case function (dap_pronaf_pf_consultar). There is no consistent verb_noun or stylistic pattern.
Tool Count4/5
Seven tools is a reasonable number for a server that combines platform utilities with a domain-specific query. However, the marketplace tool is a mega-tool that could be split into multiple tools, slightly inflating the effective surface.
Completeness3/5
The server covers platform operations well (auth, connection, version, bug reporting, toolkit info) but lacks domain-specific operations beyond the single consultation tool. There are no update or delete operations for DAP data, but that may be outside the server's intended scope.