Skip to main content
Glama

PETI (Trabalho Infantil)

by io.github.mcp-dir

peti_trabalho_infantil_consultar

Read-onlyIdempotent

Verifica o vínculo de uma pessoa com o Programa de Erradicação do Trabalho Infantil (PETI) a partir do CPF e do NIS. 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
NISYes
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 already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds context about payment requirements, credential-free access, public data classification, and LGPD responsibilities, which goes beyond the annotations without contradicting them.

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 composed of four sentences, each contributing useful information: purpose, hosting/payment, data access classification, and LGPD responsibility. It is slightly verbose due to legal disclaimers, but remains concise overall.

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?

It covers access type, payment, data sensitivity, and legal responsibilities, but lacks information about the return format or the meaning of the 'completo' parameter. Since there is no output schema, the description should have explained what the tool returns, which it does not.

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 explains that CPF and NIS identify the person, but it does not explain the optional 'completo' boolean parameter. With 0% schema description coverage, it partially compensates but leaves one parameter undocumented.

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 states a specific verb ('verifica') and resource ('Programa de Erradicação do Trabalho Infantil (PETI)') and clearly identifies the required inputs (CPF and NIS). It is well-differentiated from unrelated sibling tools like authenticate, marketplace, and report_bug.

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 clearly indicates the operational context: hosted on the platform, no credentials, pay-per-query with prepaid credit, and queries only public access data. However, it does not explicitly mention when not to use the tool or name alternative tools, though siblings are unrelated.

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

All PETI (Trabalho Infantil) 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.9/5.0
Disambiguation4/5

Most tools have distinct purposes: authenticate handles login, connect shows connection status, marketplace finds/runs MCPs, peti_trabalho_infantil_consultar queries PETI data, etc. However, connect and toolkit_info overlap in reporting connection status, which could cause minor confusion.

Naming Consistency3/5

Tool names mix styles: some are simple verbs (connect, authenticate), some are verb_noun (report_bug, show_version), one is a hyphenated branded name (peti_trabalho_infantil_consultar), and one is a pure noun (marketplace). The pattern is not uniform, though still readable.

Tool Count4/5

With 7 tools, the count is reasonable and within typical bounds. However, the server is branded as 'PETI (Trabalho Infantil)' yet only one tool directly relates to that domain, making the platform tools feel slightly excessive for the apparent purpose.

Completeness3/5

For the sole PETI-specific purpose, consulting a person's status by CPF/NIS is covered, but there are no additional operations like historical queries or batch checks. The platform management tools are comprehensive, but they are unrelated to the core domain, creating a sense of patchwork coverage.

Resources