show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Legal MCP (alternativa ao Jusbrasil)
TDQS
A4.2/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds minimal context (specifics about what versions are shown), but does not contradict 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?
Single sentence, no fluff. Front-loaded with the action 'Show' and concise resource description.
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 tool with no output schema, the description is sufficient. It fully explains what the tool does without needing additional context.
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?
No parameters exist, and schema coverage is 100%. The description adds value by specifying that it shows 'platform and adapter versions', clarifying the output beyond schema.
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?
Description clearly states it shows current MCP platform and adapter versions, using a specific verb 'show' and resource 'versions'. No sibling tool has a similar purpose.
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 guidance on when to use this tool vs alternatives. Usage is implied by its simple nature, but no context or exclusions are provided.
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
Disambiguation2/5
There is substantial overlap among the process-discovery tools: cnpj_processos, cpf_processos, djen_processos_por_parte, processos_buscar_por_nome, processos_buscar_por_documento, and legal_dossie all lead to finding the same kind of case by party/document, differing mainly by backend and sync/async details. The verbose descriptions mitigate the confusion, but an agent still has to reason through several competing entry points with unclear boundaries.
Naming Consistency2/5
The set uses domain prefixes and snake_case, but mixes English and Portuguese action verbs (djen_search_comunicacoes vs. djen_processos_por_parte; processos_get_resultado vs. processos_buscar_por_nome) and includes bare-noun names like cnpj_processos, legal_dossie, and transparencia_pep. Platform/utility tools (connect, marketplace, show_version) use a different English naming style, so no single pattern is followed.
Tool Count2/5
30 exposed tools exceeds the scale's heavy threshold and the count is inflated by platform/admin/marketplace meta-tools as well as multiple near-redundant discovery backends. A more scoped legal server could merge the process-finding variants and keep the utility/marketplace features separate.
Completeness2/5
The server covers a lot of ground—company/CPF data, DJEN and portal discovery, jurisprudence full text, monitoring, transparency, PEP, and sanctions—but there is no native current-case-status/movimentaçoes tool, and the descriptions repeatedly tell agents to enrich with datajud_* tools that are not exposed directly in this list. That is a significant workflow gap for a tool advertised as an alternative to Jusbrasil.