Skip to main content
Glama

Sanctions list entry

get_sanctions_entry
Read-only

Fetch a full SECO sanctions-list entry by ID from search_sanctions_list to inspect names, birth details, nationalities, addresses, documents, legal basis and listing history.

Instructions

Full SECO sanctions-list entry by id (from search_sanctions_list): all names and transliterations, birth dates and places, nationalities, addresses, identity documents, justification, legal basis (programme and annex), related entries and listing status/history.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_sanctions_entry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesEntry id from search_sanctions_list, e.g. '5142'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description's added value is disclosing the breadth of returned content (identifiers, legal basis, related entries, listing history). It says nothing about error behavior for a missing id or whether the response can be large, which for a detail endpoint would be useful.

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?

One sentence, front-loaded with the verb, resource, and key parameter, followed by a compact enumeration of payload sections. Every clause carries information and nothing is repeated from the schema or annotations.

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?

With no output schema, the description must carry the return shape, and it does so by enumerating the entry's sections. It is nearly complete; only the failure mode for an unknown id is left implicit.

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?

Schema coverage is 100% and the schema already constrains the id to a 1-10 digit pattern with an example. The description adds the provenance of the value (it must originate from search_sanctions_list), which is meaning beyond the schema, though no further format detail is given.

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?

States a specific verb and resource ('Full SECO sanctions-list entry by id') and immediately identifies the sibling that produces the id ('from search_sanctions_list'), so the agent can distinguish a detail lookup from a search without opening either schema.

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 parenthetical '(from search_sanctions_list)' makes the intended call sequence clear: search first, then fetch by id. It does not state what to do when the id is unknown or invalid, nor name any exclusion, so it falls short of explicit when/when-not guidance.

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

Deploy Server

Other Tools