Skip to main content
Glama

Sanctions Dataset Statistics

sanctions_stats

Retrieve statistics on sanctions dataset including total entries, lists covered, last update timestamp, and data source. Free endpoint.

Instructions

Get statistics about the sanctions dataset: total entries, lists covered, last updated timestamp, and data source information. Free endpoint.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • Handler function for sanctions_stats tool. Makes a GET request to /api/v1/sanctions/stats and returns the JSON response as text.
      async () => {
        const res = await apiGet<SanctionsStatsResponse>("/api/v1/sanctions/stats");
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(res.data, null, 2) },
          ],
        };
      },
    );
  • TypeScript interface defining the response shape for the sanctions stats endpoint.
    interface SanctionsStatsResponse {
      dataset: string;
      source: string;
      update_frequency: string;
      stats: Record<string, unknown>;
    }
  • Registration of the sanctions_stats tool on the MCP server with name, description, and empty input schema.
    server.registerTool(
      "sanctions_stats",
      {
        title: "Sanctions Dataset Statistics",
        description:
          "Get statistics about the sanctions dataset: total entries, lists covered, " +
          "last updated timestamp, and data source information. Free endpoint.",
        inputSchema: {},
      },
      async () => {
        const res = await apiGet<SanctionsStatsResponse>("/api/v1/sanctions/stats");
    
        if (!res.ok) {
          return {
            content: [
              {
                type: "text" as const,
                text: `API error (${res.status}): ${JSON.stringify(res.data)}`,
              },
            ],
            isError: true,
          };
        }
    
        return {
          content: [
            { type: "text" as const, text: JSON.stringify(res.data, null, 2) },
          ],
        };
      },
    );
  • src/index.ts:48-48 (registration)
    Call that registers all sanctions tools (including sanctions_stats) on the MCP server.
    registerSanctionsTools(server);
  • HTTP client helper used by the sanctions_stats handler to make the GET request 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?

With no annotations, the description adds some value by stating it is a free endpoint and listing returned data. However, it does not disclose other behavioral traits such as rate limits, idempotency, or whether authentication is needed.

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?

Two concise sentences deliver the purpose and a key behavioral note (free endpoint) with no unnecessary words. Information is front-loaded and easy to parse.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple no-parameter tool, the description is largely complete. It covers the main outputs and notes it is free. Missing details could include data freshness or access restrictions, but these are minor given the tool's simplicity.

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

Parameters4/5

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

The input schema has no parameters, so the description's role shifts to clarifying the output. It effectively explains what statistics are returned (total entries, lists, last updated, data source), adding meaning beyond the empty schema.

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 retrieves statistics about the sanctions dataset, listing specific fields like total entries and lists covered. This distinguishes it from sibling tools like 'sanctions_changes' and 'search_sanctions', which focus on changes and searching respectively.

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

Usage Guidelines3/5

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

The description implies use for obtaining aggregate stats and notes it is a 'free endpoint', but lacks explicit guidance on when to prefer this tool over alternatives like 'search_sanctions' or 'sanctions_changes'.

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