br-eli-mcp

br_search_case_tst

Read-onlyIdempotent

Search Brazilian Superior Labor Court (TST) rulings by free text. Retrieve full case texts and summaries using AND semantics and exact-phrase quotes.

Instructions

Search TST (labor supreme court) rulings by free text - real ruling text.

The query goes into the TST frontend's own "contendo as palavras" (AND) field - quote an expression for an exact-phrase match, e.g. "adicional de insalubridade". Returns the index's own total plus a page of records carrying the real ementa and inteiro_teor prose.

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": {
      "query": "<query>"
    },
    "name": "br_search_case_tst"
  }
}

Input Schema

Name	Required	Description	Default
`tipo`	No	document type - ``"ACORDAO"`` (default), ``"DESPACHO"``, ``"SUM"`` (sumulas), ``"OJ"`` (orientacoes jurisprudenciais), ``"PN"``, ``"DESPGP"``, ``"DESPGVP"``, ``"DESPGCG"``.	ACORDAO
`limit`	No	max results per page (default 20).
`query`	Yes	free text (AND semantics; quotes for exact phrase).

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.7.0Jul 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description adds value beyond annotations by explaining that the query goes into the TST frontend field, the return includes index total and a page with ementa and inteiro_teor. It is consistent with readOnlyHint, idempotentHint, and openWorldHint, and no contradictions exist.

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?

Three sentences, front-loaded purpose, each sentence providing essential information without redundancy. Highly concise and well-structured.

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?

With an output schema present, the description adequately covers input semantics and output structure, making it complete for the tool's complexity of 3 parameters and a simple return type.

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

Parameters5/5

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

Schema coverage is 100%, but the description enhances understanding by explaining the query field and providing an exact phrase example. It also describes the output fields, adding meaning beyond the schema alone.

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 the tool searches TST (labor supreme court) rulings by free text using real ruling text. It distinguishes from sibling tools which target other courts or legal entities, providing a specific verb and resource.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explains when to use (for TST ruling search) and details query semantics like AND and exact phrase matching. While it doesn't explicitly mention when not to use, the sibling context makes alternatives clear, and the description lacks explicit exclusion criteria.

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

Deploy Server