Returns connection status and URLs. When all providers are connected, returns authenticated:true and empty pending[]. When credentials are missing, returns connect_url for the toolkit and per-install URLs.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context about conditional return states (authenticated with pending[] versus credentials-missing with connect_url), helping the agent predict output without contradicting annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two focused sentences, front-loaded with the core purpose: 'Returns connection status and URLs.' Every sentence contributes state-specific details; no filler or repetition.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool has no parameters, no output schema, and low complexity, the description is fully adequate. It explains both major states (all connected vs. missing credentials) and the relevant response fields (authenticated, pending, connect_url).
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With zero parameters and 100% schema description coverage, parameter semantics are essentially not applicable. The baseline for zero-parameter tools is 4, and the description appropriately focuses on behavior rather than input details.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb and resource: 'Returns connection status and URLs.' It clearly defines the tool's purpose and distinguishes 'connect' as a status-check operation from sibling tools like 'authenticate,' which performs an action.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives clear conditional context: if all providers are connected, the response is authenticated:true and empty pending[]; if credentials are missing, response includes connect_urls. This implies when an agent should call the tool, though it does not explicitly contrast it with authenticate or list excluded scenarios.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
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.
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.
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.
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.