show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
OAB Cadastro de Advogados
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. The description adds no additional behavioral context beyond what the annotations convey, but the tool is simple and no extra disclosure is necessary.
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 that conveys the full purpose without any redundancy or unnecessary detail.
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?
For a simple version-check tool with no parameters and strong annotations, the description covers its purpose sufficiently. It does not detail return format, but no output schema exists and the expected output is obvious from the description.
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 0 parameters, so there is nothing to explain. Schema description coverage is 100% (trivially), and the baseline for parameter-less tools is 4.
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 clearly identifies the resource: 'current MCP platform and adapter versions.' This distinguishes it from sibling tools like authenticate, connect, and marketplace, which serve entirely different purposes.
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 usage (when you need to check platform/adapter versions) but does not explicitly contrast with sibling tools. Since the siblings are functionally unrelated, clear usage context is present, but no explicit when-to-use or alternative guidance is given.
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.7/5.0
Disambiguation4/5
Most tools have distinct roles: authentication, status, marketplace operations, version, toolkit info, bug reporting, and the single OAB lookup. However, 'marketplace' bundles many sub-actions (search, describe, invoke, install, prompts) which could be confusing, and 'connect' overlaps with 'authenticate' in terms of connection status.
Naming Consistency2/5
Naming is inconsistent: some are bare verbs (authenticate, connect), some are noun-style (marketplace, toolkit_info), one is Portuguese with underscores (oab_advogados_consultar), and others use underscores but with different conventions (report_bug, show_version). There is no clear verb_noun pattern across the set.
Tool Count4/5
Seven tools is a reasonable number for a platform server, though most of them are generic meta-tools. The count is not excessive, but the mix of domain and platform tools feels slightly awkward. Still, it is within a typical well-scoped range.
Completeness2/5
Given the server name 'OAB Cadastro de Advogados', the only domain-specific tool is a single lookup by name and registration number. There are no other OAB-related operations (e.g., listing, verifying, or detailed info). The rest are generic platform tools, making the domain coverage severely incomplete.