show_version
Read-onlyIdempotent
Show the current MCP platform and adapter versions.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
LegalOne
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?
The annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, and the description's 'Show' aligns with these traits. The description does not add behavioral context beyond those annotations, such as exact return format or what may happen in error cases, but nothing contradicts the 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?
The description is a single sentence, front-loaded with the action, and contains no redundant or filler wording. It provides exactly the necessary information with maximum conciseness.
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, idempotent version query tool, the description is complete. It tells the agent what the tool exposes and leaves no significant assumption gaps.
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 accepts zero parameters and the schema description coverage is 100%, so there is no parameter complexity for the description to clarify. The baseline of 4 is appropriate here.
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 names a specific resource: 'current MCP platform and adapter versions.' This is unambiguous and clearly differentiates the tool from the many legalone_* and other sibling tools.
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 intended use case is implied: call this tool when you need MCP platform and adapter version information. However, it does not explicitly mention alternatives such as toolkit_info or define when not to use it. Since the tool is extremely simple, the implied usage is acceptable but not fully explicit.
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.2/5.0
Disambiguation3/5
The core legalone_get/list/create/update tools are clearly separated by entity and verb, so common lookups are easy to pick. However, legalone_odata_get and legalone_request duplicate the named CRUD surface, lawsuits vs litigations are near-synonyms in a legal context, and connect/toolkit_info/authenticate have overlapping connection/status duties. Descriptions help resolve most cases, but several tool pairs could still be misselected.
Naming Consistency3/5
The majority of tools follow a consistent legalone_<verb>_<entity> pattern, which is good. But auxiliary tools break the pattern: legalone_customfield_options, legalone_odata_get, legalone_request, legalone_metadata, authenticate, connect, marketplace, report_bug, show_version, and toolkit_info use bare verbs, nouns, or platform-infrastructure names. The result is mixed conventions that remain readable but are not consistent across the whole set.
Tool Count2/5
With 45 tools, this set is well beyond the 3–15 well-scoped range and above the 25-tool threshold for too many. Many tools are repetitive CRUD variants per entity, plus several infrastructure and marketplace tools that inflate the agent's selection space. A smaller entity-focused set plus one generic OData escape hatch would have covered virtually the same functionality.
Completeness3/5
Core legal entities like lawsuits, litigations, contacts, appointments, tasks, and updates have create/get/list/update coverage. However, documents, users, areas, service types, and custom field definitions lack named update/delete helpers, and no entity has a dedicated delete tool. The generic legalone_request/odata_get escape hatches fill these gaps, but the lifecycle coverage is uneven.