show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
MPT BA: Certidão Negativa de Feitos
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?
The annotations already indicate read-only and idempotent behavior; the description does not add additional behavioral context, such as potential side effects or authentication requirements.
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, clear sentence with no unnecessary detail.
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?
Given the lack of parameters and output schema, the description fully specifies what the tool does.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters5/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has no parameters, and the description does not need to explain any because the schema is empty.
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 tool's function: showing the current MCP platform and adapter versions. It also distinguishes from sibling tools like 'authenticate' or 'connect'.
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 does not provide guidance on when to use this tool relative to others, such as when to check versions or if there are prerequisites.
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
The tools are mostly distinct in purpose: authenticate, connect, marketplace, report_bug, show_version, toolkit_info, and the domain-specific mpt_ba_cnf_consultar. There is minor overlap between connect (returns connection status and URLs) and toolkit_info (returns toolkit state including connection status), but each has a broader scope, so confusion is unlikely.
Naming Consistency2/5
Tool names are inconsistent: most are English single-word or camelCase (authenticate, connect, marketplace, report_bug, show_version, toolkit_info), while the only domain-specific tool is in Portuguese with underscores (mpt_ba_cnf_consultar). This mix of languages and conventions breaks the pattern.
Tool Count4/5
Seven tools is within the typical well-scoped range. However, most are generic MCP.AI platform support tools, with only one tool directly serving the stated domain (Certidão Negativa). This slightly dilutes the server's apparent purpose but is not excessive.
Completeness4/5
For the domain of querying negative certificates, the single mpt_ba_cnf_consultar tool covers the core operation, and the supporting platform tools handle auth, connection, and state. There are no obvious missing operations for a simple query service, though one might expect a history or listing tool, which is absent.