br-eli-mcp

br_get_case_tst

Read-onlyIdempotent

Retrieve a single TST ruling by CNJ process number, returning the full ruling text (ementa and inteiro teor).

Instructions

Fetch one TST ruling by its exact CNJ unified process number - real ruling text (ementa + inteiro_teor).

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": {
      "numero_processo": "<numero_processo>"
    },
    "name": "br_get_case_tst"
  }
}

Input Schema

Name	Required	Description	Default
`tipo`	No	document type (default ``"ACORDAO"``).	ACORDAO
`numero_processo`	Yes	CNJ unified process number, formatted (``"21036-38.2019.5.04.0021"``) or as the raw 20 digits. The fifth segment is 5 (Justica do Trabalho) for every TST case.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Jul 14, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already indicate readOnlyHint=true. The description adds value by specifying the returned content ('real ruling text with ementa + inteiro_teor'), which clarifies the behavioral output beyond 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, front-loaded sentence with no wasted words. It efficiently conveys the core purpose and key detail about the returned content.

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?

Given the presence of an output schema, the description does not need to explain return structure. It covers the essential purpose, parameter nuances, and a key behavioral trait (returning full ruling text). The tool is well-documented for its complexity.

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 schema covers both parameters (100% coverage). The description adds meaningful detail: the formatting rule for numero_processo (fifth segment 5) and the default for tipo, which enhances understanding beyond the schema alone.

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 tool fetches a TST ruling by exact CNJ process number and returns the full text. However, it does not explicitly differentiate from sibling tools like br_search_case_tst, which could be used for non-exact searches.

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 description implies usage when you have the exact CNJ number, but does not explicitly state when not to use this tool (e.g., for fuzzy search) or mention alternative tools like br_search_case_tst. No exclusions or context provided.

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

Deploy Server