show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Vínculos Societários
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A4.1/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, indicating a safe read operation. The description adds what information is shown (platform and adapter versions) but does not disclose additional behavioral details such as network calls or return format.
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 action 'Show', and contains no extraneous words or details. Every word earns its place.
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?
The tool is extremely simple with no parameters, no output schema, and annotations covering safety. The description sufficiently explains the tool's purpose without missing information necessary for invocation.
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?
There are zero parameters, and the input schema is empty, so the description needs to add no parameter meaning. The baseline for 0-parameter tools is 4, and the description correctly does not introduce unnecessary complexity.
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 shows the current MCP platform and adapter versions, using a specific verb 'show' and a specific resource. It is unambiguous and distinct from sibling tools like toolkit_info or report_bug.
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 description implies use when version information is needed, but it does not explicitly state when to use versus alternatives or any exclusions. There is no guidance comparing it to similar info tools like toolkit_info.
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 tool has a broadly distinct role—auth, status, marketplace, version, toolkit info, and the domain query. However, `connect` and `toolkit_info` both report connection state, and `marketplace` bundles many sub-operations (search, invoke, install, prompts) into one tool, which can blur boundaries.
Naming Consistency2/5
Naming is inconsistent: platform tools mix verb-led names (authenticate, connect, report_bug, show_version) with noun-led names (marketplace, toolkit_info), and the single domain tool uses a Portuguese noun-based phrase (vinculos_societarios_consultar). This mixing of language and pattern makes the set feel arbitrary.
Tool Count2/5
The server is named 'Vínculos Societários' but only one of seven tools is domain-specific; the other six are generic platform management tools that could belong to any MCP server. The domain tool count is too thin, while the meta-tool count is oversized relative to the stated purpose.
Completeness2/5
For the domain of corporate relationship lookup, only a single consult operation is provided. There are no supporting tools for data preview, history, export, or related searches, and no obvious operations to complement the core query. The platform helpers do not contribute to domain coverage.