legalone_create_tasks
Cria um(a) Tarefas/providências (o prazo vem no campo deadLine) (OData POST /Tasks). data = corpo da entidade conforme a API oficial.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes |
LegalOne
Schema Changelog
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
- First observed
TDQS
B3.3/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses the HTTP method (POST) and the endpoint, as well as noting that the deadline is in the 'deadLine' field. However, it does not elaborate on side effects, permissions, or response behavior.
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 concise, one sentence, and directly to the point without unnecessary details.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness2/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
The description lacks information about return values, error handling, or any other context that would help a caller understand the full behavior. Given the minimal schema, it leaves many questions unanswered.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters2/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description explains that the 'data' parameter is the entity body according to the official API, but it does not detail the structure or required fields of that object. The schema itself is vague, and the description does not compensate.
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 clearly states that the tool creates a 'Tarefas' (task) via a POST /Tasks OData endpoint, making its purpose unambiguous. It is specific to tasks, distinguishing it from other create tools for different entities.
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?
The description does not provide any explicit guidance on when to use this tool versus alternatives, such as scenarios or prerequisites. It only states the action without contextual usage instructions.
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.