Skip to main content
Glama

Sanctions Screening

by io.github.pipeworx-io

Search Within a Source

search_within
Read-onlyIdempotent

Semantic search INSIDE a fetched record. Pass the text you already pulled (e.g. a SEC 10-K body, an article, a long tool result) plus a natural-language query; get back the top-N passages with character offsets and similarity scores. Use when the record is too big to cram into the prompt — search_within saves context, returns only the passages that matter, and every passage carries an offset so the agent can verify a verbatim quote. Pairs with ask_pipeworx_grounded: fetch with the gateway, ground over the relevant passages instead of the whole document. BGE-base-en embeddings + cosine over 500-char overlapping windows; cap is 200K chars (longer inputs are truncated and flagged).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
textYesThe document text to search inside (max ~200K chars).
limitNoMax passages to return (1-20, default 5).
queryYesNatural-language query — what passages do you want? E.g. "supply-chain risk", "fiscal year 2024 revenue", "drug interactions with warfarin".

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark this as readOnly/idempotent/non-destructive. The description adds rich context beyond annotations: returns passages with character offsets and similarity scores, uses BGE-base-en embeddings with 500-char overlapping windows, and has a 200K char cap with truncation flagging. This is exactly the kind of behavioral detail agents need.

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 well-structured: it starts with the core action, then the use case, then complementary tool, then technical details. Every sentence carries information; no fluff. Despite moderate length, it remains tight and front-loaded.

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?

Given no output schema, the description explains the return shape (passages with offsets and similarity scores). It also covers edge behavior (truncation), technical implementation, and integration with a sibling tool. Combined with clear parameter schemas and annotations, this provides a complete picture.

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% so baseline is 3. The description adds meaning by framing 'text' as 'already pulled' content, clarifying 'query' as natural-language, and explaining the purpose of 'limit'. It reinforces the cap and return format, adding some value beyond the 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 states a specific verb+resource: 'Semantic search INSIDE a fetched record', clearly distinguishing it from sibling tools like ask_pipeworx_grounded. It also contrasts with whole-document grounding, making the tool's unique scope explicit.

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

Usage Guidelines5/5

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

Explicit guidance is given: use when the record is too big to cram into the prompt. It also pairs with ask_pipeworx_grounded (fetch with gateway, ground over relevant passages), and gives concrete examples of input text. Alternatives and complementary tools are named.

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

All Sanctions Screening 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.8/5.0
Disambiguation2/5

Many tools have overlapping purposes: ask_pipeworx and ask_pipeworx_beta are nearly identical, several prediction-market tools (bet_research, polymarket_edges, polymarket_arbitrage, polymarket_fill_risk, polymarket_kalshi_spread) cover similar territory, and research/verification tools (ask_pipeworx, ask_pipeworx_grounded, deep_research, validate_claim) blur together. The three sanctions tools are distinct, but the rest of the set creates frequent misselection risk.

Naming Consistency3/5

All tool names use snake_case, which is consistent, but the verb/noun ordering varies unpredictably (expectation vs entity_profile vs sanctions_screen vs scan_dependency). There is no dominant pattern like verb_noun, though names are readable.

Tool Count2/5

With 34 tools, the server is over-scoped, especially given its narrow 'Sanctions Screening' title. Many tools are duplicative (ask_pipeworx_beta duplicates ask_pipeworx; scan_competitor_ai_presence wraps ai_visibility_check), and the bulk are unrelated to the stated purpose. The count feels bloated.

Completeness3/5

The three sanctions tools (screen, entry, lists) cover the core read-only workflow well, but the server is mislabeled: most of the 34 tools are generic data/Pipeworx features unrelated to sanctions. For the broad data domain the set is fairly complete, but for the apparent 'Sanctions Screening' purpose it is both over- and under-scoped, with no bulk screening or list management.

Resources