Skip to main content
Glama
Sign In

Pyfile LLM & Data API

by io.github.pyfile-toolkit
OverviewDiscussionsAdmin

ofac_sanctions_search

Search the US Treasury OFAC SDN sanctions list by entity name (KYB/AML screening).

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": {
      "q": "<q>"
    },
    "name": "ofac_sanctions_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesEntity name to screen, e.g. a company name.
limitNoMax matches (default 10).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It reveals the authoritative source (US Treasury OFAC SDN) but says nothing about match semantics (exact vs fuzzy), result format, rate limits, or auth requirements. For a screening tool whose match behavior determines compliance decisions, this is a notable gap.

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?

A single tight sentence with the verb and data source front-loaded and zero filler. Every clause earns its place.

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

Completeness3/5

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

For a simple two-parameter lookup with no annotations or output schema, the description conveys the essential source and purpose. It omits anything about result interpretation or matching behavior, which an agent screening entities would benefit from knowing.

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%, with both q and limit documented in the schema, so the baseline is 3. The description's 'by entity name' corroborates the q parameter but adds no syntax, format, or matching hints beyond what the schema already says.

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?

States a specific verb and resource: search the US Treasury OFAC SDN sanctions list, scoped to entity name. It names the exact data source, which is meaningful. It does not explicitly differentiate from the sibling kyb_screening, which likely overlaps in intent.

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 parenthetical '(KYB/AML screening)' implies the compliance context in which this tool is used, but there is no explicit when-to-use, when-not-to-use, or named alternative (e.g. kyb_screening). Usage is inferable rather than stated.

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

All Pyfile LLM & Data API toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources