MCP Advbox Server

advbox_create_movement

Create a new movement or update for a lawsuit by providing its ID and description. Optionally set the movement date to log case activity in the legal management system.

Instructions

Create a new movement/update for a lawsuit

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "lawsuit_id": "<lawsuit_id>",
      "description": "<description>"
    },
    "name": "advbox_create_movement"
  }
}

Input Schema

Name	Required	Description
`date`	No	Movement date (YYYY-MM-DD)
`lawsuit_id`	Yes	Lawsuit ID
`description`	Yes	Movement description

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 9, 2026

TDQS

B3.1/5.0

Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must disclose behavioral traits. It only states 'Create', implying a write operation, but does not explain side effects, authentication needs, validation rules, or what happens if the lawsuit does not exist. This lack of detail leaves significant ambiguity for an agent.

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 concise sentence that immediately conveys the core action and resource. No filler words or redundant phrasing, making it highly efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple create operation with fully described parameters, the description is minimally adequate. However, it lacks any mention of required context like the need for an existing lawsuit or the meaning of a 'movement' in this domain. With no annotations or output schema, this gap leaves the agent to infer critical details from the tool name alone.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the parameter semantics are already fully documented in the input schema. The description adds no additional context about parameter usage or relationships, meeting the baseline but not exceeding it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'Create' and the resource 'movement/update for a lawsuit', making it evident this tool adds a new record associated with a case. It distinguishes itself from related siblings like advbox_create_lawsuit and advbox_update_lawsuit by referring to 'movement', though the term 'movement/update' is slightly ambiguous.

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?

There is no guidance on when to use this tool versus alternatives or any prerequisites such as requiring an existing lawsuit. The description is a bare statement of functionality and does not mention typical workflows or exclusions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server