Skip to main content
Glama

MPT (Ministério Público do Trabalho)

by io.github.mcp-dir

mpt_consultar

Read-onlyIdempotent

Consulta registros de uma pessoa ou empresa no Ministério Público do Trabalho (MPT) 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

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds meaningful context: data is public, not private, and the client is responsible for LGPD compliance, which informs safe usage 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.

Conciseness4/5

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

The description is compact, covering purpose, payment, data nature, and legal responsibility in a few sentences without redundancy. It is front-loaded with the main function.

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 explains the purpose, payment model, and data access level, but does not describe the response shape or clarify the 'completo' parameter. With no output schema, this leaves gaps for the agent.

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

Parameters2/5

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

Schema description coverage is 0%, and the description mentions CPF, CNPJ, and region but omits the 'completo' parameter. It also says 'CPF ou CNPJ' while the schema requires both, creating ambiguity. This fails to adequately clarify parameter usage.

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 it queries MPT records using CPF/CNPJ and region, distinguishing it from unrelated siblings like authenticate and marketplace. The verb 'Consulta' and resource are specific and unambiguous.

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 specifies that no credentials are needed and that queries are paid via prepaid credit, framing when to use it. It does not explicitly mention alternatives or exclusions, but sibling tools are functionally distinct, so context is sufficient.

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

All MPT (Ministério Público 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.8/5.0
Disambiguation3/5

The marketplace tool bundles many sub-actions (search, describe, invoke, install, prompts, etc.) that overlap with report_bug, connect, and toolkit_info, making it unclear which tool to choose for a given task. However, mpt_consultar is clearly distinct, and the core tools are mostly separable.

Naming Consistency2/5

Tool names mix single verbs (authenticate, connect), nouns (marketplace, toolkit_info), Portuguese verbs (mpt_consultar), and snake_case verb_noun patterns (report_bug, show_version). There is no consistent naming convention, which reduces predictability.

Tool Count4/5

Seven tools is a reasonable count for a platform server covering authentication, connection status, marketplace access, bug reporting, versioning, and toolkit state. The broad scope justifies the number, though one tool (marketplace) carries a disproportionate amount of functionality.

Completeness4/5

The platform lifecycle is well-covered: authentication, connection checks, marketplace exploration/invocation/installation, billing, bug reporting, and version/info. The mpt_consultar tool addresses the specific MPT domain query. Minor gaps exist, such as no dedicated credential management beyond authenticate, but core workflows are not dead-ended.

Resources