Skip to main content
Glama

Search Sanctions

search_sanctions

Search global sanctions lists to identify restricted entities by name, alias, address, or country. Access OFAC, EU, UN, and UK sanctions data with relevance-ranked results.

Instructions

Full-text search across all sanctions entries. Search by name, alias, address, country, or program. Returns matching entries ranked by relevance. Cost: $0.009 per query. Source: OFAC SDN, EU, UN, UK lists.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
qYesSearch query (name, alias, address, country, etc.)
limitNoMaximum results (default 25)

Implementation Reference

  • Handler function for the search_sanctions tool. It makes an API call to /api/v1/sanctions/search and processes the response.
      async ({ q, limit }) => {
        const res = await apiGet<SanctionsQueryResponse>(
          "/api/v1/sanctions/search",
          { q, limit: limit ?? 25 },
        );
    
        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 result(s).`;
        const json = JSON.stringify(data, null, 2);
    
        return {
          content: [{ type: "text" as const, text: `${summary}\n\n${json}` }],
        };
      },
    );
  • Input schema definition for the search_sanctions tool.
    {
      title: "Search Sanctions",
      description:
        "Full-text search across all sanctions entries. Search by name, alias, address, " +
        "country, or program. Returns matching entries ranked by relevance. " +
        "Cost: $0.009 per query. Source: OFAC SDN, EU, UN, UK lists.",
      inputSchema: {
        q: z.string().describe("Search query (name, alias, address, country, etc.)"),
        limit: z
          .number()
          .int()
          .min(1)
          .max(100)
          .optional()
          .describe("Maximum results (default 25)"),
      },
    },
  • Tool registration for search_sanctions.
    server.registerTool(
      "search_sanctions",
Behavior4/5

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

With no annotations provided, the description carries full burden and adds valuable behavioral context: it discloses the cost ('$0.009 per query'), data sources, and ranking behavior ('ranked by relevance'). However, it doesn't mention rate limits, authentication requirements, or potential limitations of the search algorithm, leaving some behavioral aspects uncovered.

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?

The description is efficiently structured in three sentences: purpose/scope, searchable fields/ranking, and cost/sources. Every sentence adds essential information with zero waste, making it appropriately sized and front-loaded with the core functionality.

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 search tool with no annotations and no output schema, the description provides good context: purpose, search scope, ranking, cost, and sources. However, it doesn't describe the return format (what fields are included in results) or pagination behavior, which would be helpful given the lack of output schema. The cost disclosure is particularly valuable for a paid service.

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 description coverage is 100%, so the schema already documents both parameters thoroughly. The description adds marginal value by implying the 'q' parameter accepts various entity types (name, alias, address, etc.) and that results are ranked, but doesn't provide additional syntax or format details beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.

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 performs a 'full-text search across all sanctions entries' with specific searchable fields (name, alias, address, country, program) and mentions the ranking method ('ranked by relevance'). It distinguishes itself from sibling tools like 'sanctions_changes' and 'sanctions_stats' by focusing on search functionality rather than changes or statistics.

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 usage context by specifying searchable fields and sources (OFAC SDN, EU, UN, UK lists), but doesn't explicitly state when to use this tool versus alternatives like 'screen_sanctions' or other search tools. It provides some guidance through the search scope but lacks explicit when/when-not instructions or named alternatives.

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