Skip to main content
Glama

Interpol

by io.github.mcp-dir

interpol_consultar

Read-onlyIdempotent

Verifica se um nome consta nas notificações da Interpol, a partir do nome, sobrenome e data de nascimento, para diligência de compliance e AML. 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
NomeYes
completoNo
SobrenomeYes
DataNascimentoYes

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 indicate readOnly and non-destructive. The description adds valuable behavioral context: requires prepaid credit ('pague por consulta'), accesses public data only, and includes LGPD data-controller responsibilities. This goes beyond the annotations and helps the agent set user expectations.

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 focused sentences, each serving a purpose: purpose, hosting/payment, data classification, and legal responsibility. It is concise, without redundancy, and front-loads the primary action.

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 purpose, usage context, payment, data sensitivity, and legal aspects. However, it does not describe the return value or output format, which is notable since there is no output schema. It also leaves the 'completo' parameter unexplained, making the description incomplete for full tool usage.

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 explicitly lists 'nome, sobrenome e data de nascimento' matching three required parameters, but the 'completo' boolean parameter is not mentioned. It does not provide format details for 'DataNascimento'. Since schema description coverage is 0%, the description only partially compensates for the missing parameter explanations.

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's function: 'Verifica se um nome consta nas notificações da Interpol' (checks if a name appears in Interpol notifications), specifying the resource (Interpol notifications) and the inputs (nome, sobrenome, data de nascimento). It is easily distinguished from sibling tools, which are unrelated meta-tools.

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?

Provides clear context for when to use: 'para diligência de compliance e AML' (for compliance and AML due diligence). It also sets expectations about no credentials and prepaid credit. However, it does not explicitly mention when not to use it or name alternatives, though no alternatives exist among siblings.

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

All Interpol 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
Disambiguation5/5

Each tool has a clearly distinct purpose: authentication, connection status, Interpol data lookup, marketplace operations, bug reporting, version display, and toolkit state. There is no meaningful overlap that would confuse an agent.

Naming Consistency2/5

Tool naming is inconsistent: some are single words (authenticate, connect, marketplace), some are snake_case verb_noun compounds (report_bug, show_version), and one is a non-English prefixed verb (interpol_consultar). This mixed style makes the naming pattern unpredictable.

Tool Count4/5

Seven tools is within a reasonable range, but the set is split between Interpol-specific functionality and generic MCP platform management, making the server's scope feel somewhat unfocused. Still, the count itself is not excessive.

Completeness3/5

The platform management side is fairly covered (auth, connection, toolkit info, marketplace, bug reporting), but the Interpol-specific side consists of only one tool, leaving no options for broader Interpol data queries or follow-up operations. This makes the server feel incomplete relative to its name.

Resources