Skip to main content
Glama

Processos TRT (Justiça do Trabalho)

by io.github.mcp-dir

trt_processos_consultar

Read-onlyIdempotent

Consulta processos de uma pessoa ou empresa no Tribunal Regional do Trabalho (TRT) a partir do CPF ou CNPJ e região. Hospedado pela plataforma, sem credenciais, pague por consulta com crédito pré-pago. Consulta informação de ACESSO PÚBLICO em bases e fontes oficiais (a mesma disponível ao cidadão), não é dado privado nem sigiloso. O cliente é o controlador dos dados e responde pela finalidade legítima (LGPD).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
CpfYes
CnpjYes
RegiaoYes
completoNo

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations mark the tool as read-only and idempotent, and the description adds further context: it queries public-access data, clarifies it is not private, and notes LGPD responsibilities. It also mentions the payment model, which is a behavioral trait not in annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is 2 sentences and front-loads the core purpose. It packs essential operational and legal details without fluff, though it is dense.

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?

The description covers data source, payment, and legal aspects, but with no output schema it omits any indication of return values or error behavior. The CPF/CNPJ ambiguity is also unresolved, weakening completeness.

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 description names CPF/CNPJ and region as query inputs, giving them meaning beyond the schema's bare type declarations. However, it does not describe the optional 'completo' boolean, and the schema marks both Cpf and Cnpj as required, which contradicts the 'ou' (or) phrasing in the description, leaving ambiguity.

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 opens with 'Consulta processos de uma pessoa ou empresa no TRT', clearly stating the action (query) and the resource (labor court cases). It specifies the inputs (CPF/CNPJ and region), distinguishing it from the sibling tools which are unrelated (auth, marketplace, etc.).

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?

The description explains the operational context: hosted on the platform, requires no credentials, and is paid per query with prepaid credit. It does not explicitly state alternatives or exclusions, but the unique purpose among siblings makes this less critical.

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

All Processos TRT (Justiça do Trabalho) toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation4/5

Most tools serve distinct platform functions (auth, connection status, marketplace, bug reporting, version, toolkit info), and the TRT consultation tool is clearly separate. Some overlap exists between 'authenticate' and 'connect' (both deal with connection/auth state), but their roles are sufficiently differentiated by descriptions.

Naming Consistency2/5

Tool names mix English and Portuguese, and follow no uniform pattern: some are lowercase verbs (authenticate, connect), one is an underscored lowercase noun (toolkit_info), and the domain tool uses a Portuguese verb_noun structure (trt_processos_consultar). This inconsistency makes the set feel disjointed.

Tool Count2/5

With 7 tools, the count is not excessive, but the scope is muddled: six generic platform tools are paired with one domain-specific tool. For a server named 'Processos TRT', the majority are unrelated, while for a platform server, the TRT tool seems out of place. The tool set lacks a clear, focused purpose.

Completeness2/5

For the apparent TRT domain, only a single query operation is provided (consult by CPF/CNPJ). There is no support for fetching process details by number, checking status, or any other related operations. The platform tools add broad capabilities, but they do not address gaps in the domain surface, leaving the server incomplete for its stated purpose.

Resources