show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Tribunal TRF5: Processo
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
A3.9/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, and the description's 'Show' aligns with these. The description adds minimal behavioral context beyond the annotations, but there is little else to disclose for a read-only version retrieval operation.
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 states the action and the subject with no filler or redundancy. 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?
Given the tool's simplicity (zero parameters, no output schema, and comprehensive annotations), the description fully covers what the tool does. It provides sufficient information for an agent to select and invoke it correctly without ambiguity.
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 zero parameters, so the schema provides full coverage by definition. The description needs no additional parameter explanation, aligning with the baseline of 4 for parameterless tools.
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 the specific verb 'Show' and names the exact resource ('current MCP platform and adapter versions'), making the tool's function unmistakable. It effectively differentiates from sibling tools like 'authenticate', 'marketplace', and 'report_bug' 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 Guidelines2/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives, and no exclusions or alternative recommendations are mentioned. For a simple version-check tool, usage is implied but not explicitly stated.
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.9/5.0
Disambiguation4/5
Most tools are clearly distinct: marketplace, report_bug, show_version, toolkit_info, and the consultation tool each serve unique functions. The only potential confusion is between 'authenticate' and 'connect', but their descriptions clarify that one handles token acquisition and the other reports connection status.
Naming Consistency2/5
Tool names mix conventions inconsistently: single-word verbs (authenticate, connect), snake_case verb-noun (report_bug, show_version), noun-based (marketplace, toolkit_info), and a Portuguese snake_case domain tool (tribunal_trf5_processo_consultar). While readable, there is no unified naming pattern.
Tool Count5/5
With 7 tools, the server is well-scoped. Six platform management/utility tools plus one domain-specific consultation tool form a compact set where each tool earns its place, and the count is well within the ideal range.
Completeness4/5
The server's primary domain purpose is consulting TRF5 processes, and the single domain tool fulfills that core action. Platform coverage via marketplace and toolkit_info is solid. Minor gaps exist—such as specialized process actions or additional query parameters—but the core workflow is not broken.