Skip to main content
Glama

Swiss sanctions programmes

list_sanctions_programs
Read-only

Retrieve all Swiss sanctions programmes from the SECO list, including legal basis, UN/EU/CH origin, annexes, and current counts of listed individuals, entities, and objects.

Instructions

All Swiss sanctions programmes (embargo ordinances) on the SECO list with their legal basis, origin (UN/EU/CH), annexes/measure sets and the number of currently listed individuals, entities and objects.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.3

TDQS

A3.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the data content and provenance (SECO, UN/EU/CH origin, counts), but does not disclose freshness, caching, ordering, or pagination behavior beyond those annotations.

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?

It is a single, front-loaded sentence that identifies the resource and lists the key returned fields with no filler. Every clause contributes to what the tool returns.

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 no-parameter list tool with no output schema and no annotated safety gaps, the description is fairly complete: it explains the data source, origin breakdown, and per-programme counts. It could still mention ordering or pagination, but the essential shape of the result is conveyed.

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 tool takes zero parameters, so the baseline is 4. There are no parameter semantics to explain, and the description appropriately focuses on the returned content instead.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a clear resource: all Swiss sanctions programmes on the SECO list, and enumerates the returned fields (legal basis, origin, annexes/measure sets, counts). It is distinguishable from search_sanctions_list and get_sanctions_entry because it refers to programmes rather than individual entries, though it does not explicitly name those siblings.

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?

Usage is only implied: an agent can infer this tool is for enumerating programmes, while search_sanctions_list and get_sanctions_entry handle entries. There is no explicit when-to-use or when-not-to-use guidance, and no alternative is mentioned.

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