Skip to main content
Glama

Sanções Canadá (SEMA)

by io.github.mcp-dir

sancoes_canada_consultar

Read-onlyIdempotent

Verifica se um nome consta na lista de sanções internacionais do Canadá (SEMA), 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

Schema Changelog

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

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds operational context: no credentials required, pay-per-query cost, and LGPD legal responsibilities for the controller, going 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 three sentences, starting with the core purpose, then providing cost and access details, and finally the legal disclaimer. It is efficient with no redundant phrasing, though the LGPD sentence adds length without directly aiding tool invocation.

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 tool is simple and annotations cover safety, but the description omits any explanation of the expected return value or the behavior of the 'completo' parameter. Since there is no output schema, these gaps make the description incomplete for an agent needing to interpret results.

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

Parameters1/5

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

The input schema has two parameters with zero description coverage, and the description fails to explain the meaning of 'completo' or explicitly map 'Nome' to the name parameter. This leaves the agent without essential guidance on how to set parameters, especially the optional boolean.

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 checks a name against Canada's international sanctions list (SEMA), using a specific verb and resource. It is distinct from siblings like authenticate, connect, and marketplace, leaving no ambiguity about its function.

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 explicitly positions the tool for compliance and AML due diligence, and notes the cost model (prepaid credits) and the public access nature of the data. It does not discuss when not to use this tool or mention alternative sanctions lists, but the context for appropriate use is clearly stated.

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

All Sanções Canadá (SEMA) 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

B3.4/5.0
Disambiguation2/5

The marketplace tool is a catch-all that overlaps with report_bug (which it also mentions it can do), connect, and toolkit_info in terms of status and management. The single domain-specific tool, sancoes_canada_consultar, is clearly distinct from the platform utilities, but the utility tools have unclear boundaries among themselves.

Naming Consistency2/5

Names mix single verbs (authenticate, connect), nouns (marketplace, toolkit_info), and snake_case (report_bug, show_version, sancoes_canada_consultar). The Portuguese domain tool breaks the otherwise English naming convention, and there is no consistent verb_noun pattern across the set.

Tool Count3/5

Seven tools is a reasonable count, but six are generic platform utilities (auth, connection, marketplace, bug reporting, version, state) while only one serves the Canada sanctions domain. The scope feels split between a platform admin toolkit and a specific data service, making the count less coherent for the server's stated purpose.

Completeness2/5

The domain surface is extremely thin: only a single lookup operation for Canada sanctions, with no additional query types, listing options, or batch operations. The other tools address platform lifecycle, not the sanctions domain, leaving obvious gaps for a compliance-focused server (e.g., different sanction lists, detailed results, watchlists).

Resources