Skip to main content
Glama

Open Sanctions

by io.github.pipeworx-io

Recall

recall
Read-onlyIdempotent

Retrieve a value previously saved via remember, or list all saved keys (omit the key argument). Use to look up context the agent stored earlier — the user's target ticker, an address, prior research notes — without re-deriving it from scratch. Scoped to your identifier (anonymous IP, BYO key hash, or account ID). Pair with remember to save, forget to delete.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
keyNoMemory key to retrieve (omit to list all keys)

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already indicate readOnly, destructive false, idempotent. Description adds value by explaining listing behavior when key omitted and scoping to identifier. No contradictions.

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 sentences, front-loaded with purpose, no wasted words. Highly concise and structured.

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

Completeness5/5

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

Tool has one optional parameter and no output schema; description adequately explains behavior (retrieve value or list keys) and scoping, fully covering the needed context.

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%, so baseline 3. Description adds minor clarification on omitting key to list, but does not provide significant extra meaning beyond 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 the tool retrieves a value saved via remember or lists all keys, using specific verbs 'retrieve' and 'list'. It distinguishes from sibling tools like remember and forget.

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?

Provides clear context on when to use: looking up stored context like tickers or notes. Mentions scoping and pairing with remember/forget. Lacks explicit when-not usage, but sufficient guidance.

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

All Open Sanctions toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.6/5.0
Disambiguation2/5

Multiple tools have overlapping purposes, especially the ask_pipeworx variants (ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, deep_research, bet_research) which all serve to query data but with subtle differences. An agent would struggle to distinguish which to use without deep understanding of their nuances.

Naming Consistency3/5

Most tool names follow a verb_noun or noun_noun pattern in snake_case, but there are exceptions like 'forget', 'recall', 'remember' which are single verbs, and names like 'ask_pipeworx' mix verb and proper noun. Overall pattern is discernible but not uniform.

Tool Count2/5

33 tools is high for a server named 'Open Sanctions' which implies a focused domain. The tool set spans sanctions, meta-querying, prediction markets, memory, subscriptions, and more, making it feel bloated and unfocused relative to the server's name.

Completeness2/5

For a sanctions server, only two tools (search_entities, get_entity) directly address the domain, missing obvious operations like update, delete, or list. Many tools are unrelated to sanctions, leaving the core domain incomplete.

Resources