Skip to main content
Glama
Sign In
MCP Advbox Server

MCP Advbox Server

by JonasSousaAP
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

advbox_get_publications

Fetch all publications tied to a specific lawsuit by supplying the lawsuit ID. Obtain legal publication records directly from the Advbox legal management system.

Instructions

Get publications for a specific 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>"
    },
    "name": "advbox_get_publications"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawsuit_idYesLawsuit ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/5.0
Behavior1/5

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

No annotations are present, so the description alone must convey behavioral traits. It only restates the tool's basic function and gives no information about return format, error behavior, ordering, pagination, or permission requirements. The description adds no transparency beyond what the name implies.

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, front-loaded sentence with no filler words. It is as concise as possible while conveying the core action.

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?

For a tool with no output schema and no annotations, the description fails to explain what a 'publication' is, the nature of the response, or any edge cases. It is adequate only for conveying the high-level purpose, but lacks context on behavior and results, making it incomplete for an agent to reliably use.

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?

The schema already describes lawsuit_id as an integer 'Lawsuit ID' with 100% coverage. The description doesn't add any additional semantic detail beyond acknowledging the lawsuit context, so the schema carries the explanatory weight. Baseline 3 is appropriate.

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 'Get' with a clear resource 'publications' and scope 'for a specific lawsuit', distinguishing it from sibling tools like get_lawsuit or get_lawsuit_history. It is unambiguous and action-oriented.

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 about when to use this tool versus alternatives, or any prerequisites such as whether a lawsuit must exist. There is no mention of exclusions or fallback tools, leaving the agent without direction on selection.

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

Deploy Server

Other Tools