Skip to main content
Glama

Sanctions Changes

sanctions_changes

Get recent changes to sanctions lists, including additions, removals, and modifications. Specify a timestamp to retrieve updates since that time.

Instructions

Get recent changes to sanctions lists since a given timestamp. Shows additions, removals, and modifications to sanctioned entities. Cost: $0.005 per query. Source: Consolidated sanctions lists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sinceYesISO 8601 timestamp to get changes since (e.g. 2026-03-01T00:00:00Z)
limitNoMaximum results (default 50)

Implementation Reference

  • The async handler function for the 'sanctions_changes' tool. It calls the API endpoint /api/v1/sanctions/changes with 'since' and 'limit' parameters, processes the response, and returns results with a summary showing the count of changes found.
      async ({ since, limit }) => {
        const res = await apiGet<SanctionsQueryResponse>(
          "/api/v1/sanctions/changes",
          { since, limit: limit ?? 50 },
        );
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        const { count, data } = res.data;
        const warn = stalenessWarning(res);
        const summary = `${warn}Found ${count} sanctions change(s) since ${since}.`;
        const json = JSON.stringify(data, null, 2);
    
        return {
          content: [{ type: "text" as const, text: `${summary}\n\n${json}` }],
        };
      },
    );
  • The registration call for 'sanctions_changes' including its metadata (title, description, cost) and input schema defining 'since' (ISO 8601 timestamp, required) and 'limit' (max results, optional, default 50) parameters.
    server.registerTool(
      "sanctions_changes",
      {
        title: "Sanctions Changes",
        description:
          "Get recent changes to sanctions lists since a given timestamp. Shows additions, " +
          "removals, and modifications to sanctioned entities. " +
          "Cost: $0.005 per query. Source: Consolidated sanctions lists.",
        inputSchema: {
          since: z
            .string()
            .describe("ISO 8601 timestamp to get changes since (e.g. 2026-03-01T00:00:00Z)"),
          limit: z
            .number()
            .int()
            .min(1)
            .max(100)
            .optional()
            .describe("Maximum results (default 50)"),
        },
      },
  • src/index.ts:48-48 (registration)
    Registration of the sanctions tools module (registerSanctionsTools) into the MCP server, which includes the 'sanctions_changes' tool.
    registerSanctionsTools(server);
  • The apiGet helper used by the sanctions_changes handler to make HTTP GET requests to the Verilex API.
    export async function apiGet<T = unknown>(
      path: string,
      params?: Record<string, string | number | undefined>,
    ): Promise<ApiResponse<T>> {
      const url = buildUrl(path, params);
    
      const headers: Record<string, string> = {
        Accept: "application/json",
        "User-Agent": "verilex-mcp-server/0.1.0",
      };
    
      // Forward x402 payment token if present in env (for paid endpoints)
      const paymentToken = process.env.VERILEX_PAYMENT_TOKEN;
      if (paymentToken) {
        headers["X-Payment-Token"] = paymentToken;
      }
    
      const res = await fetch(url, { headers });
      const data = (await res.json()) as T;
    
      const stale = res.headers.get("X-Data-Stale");
      const lastUpdated = res.headers.get("X-Data-Last-Updated");
      const ageSeconds = res.headers.get("X-Data-Age-Seconds");
    
      return {
        ok: res.ok,
        status: res.status,
        data,
        stale: stale === "true",
        lastUpdated: lastUpdated ?? undefined,
        ageSeconds: ageSeconds ? Number(ageSeconds) : undefined,
      };
    }
Behavior3/5

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

No annotations provided, so description carries full burden. It discloses cost ($0.005 per query) and source (Consolidated sanctions lists), but lacks details on rate limits, pagination, side effects, or how results are ordered. Basic transparency but incomplete.

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

Conciseness5/5

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

Three short sentences: first states purpose, second clarifies output type, third adds cost and source. No fluff, front-loaded, efficient.

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?

No output schema, so description should explain return structure. It only mentions 'additions, removals, modifications' but not fields within each. No pagination or rate limit info. Adequate for a simple list tool but leaves gaps.

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?

Schema coverage is 100%; both parameters are well-described in the schema. The description adds no new meaning beyond the schema (mentions ISO 8601 format for 'since' which is already in schema, and default 50 for limit). Baseline 3 applies.

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?

Description starts with 'Get recent changes to sanctions lists since a given timestamp', clearly specifying the verb (get), resource (changes to sanctions lists), and scope (since timestamp). It further explains it shows additions, removals, modifications, which distinguishes it from siblings like search_sanctions or sanctions_stats.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool vs alternatives. It does not mention exclusions, prerequisites, or compare to other tools like search_sanctions. The cost mention is a minor hint but not explicit usage direction.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/carrierone/verilexdata-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server