Signal Oracle

VendorRisk — free preview

vendorrisk_preview

Read-only

FREE preview of counterparty risk: tracked OFAC designations + product recalls we monitor for the name. The authoritative sanctions/denied-party (CSL) + federal debarment (SAM) screening and the CLEAR→PROHIBITED risk verdict are the paid /v1/vendorrisk/check.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes	Company or individual name to screen

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	No
`note`	No
`tier`	No
`upgrade`	No
`trackedFlags`	No
`trackedFlagCount`	No

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already indicate readOnlyHint and openWorldHint. The description adds context about what data is returned (free data only) but does not disclose additional behavioral traits such as rate limits or authentication.

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 concise sentences front-load the key information. Every sentence adds value, with no redundancy or fluff.

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 the tool's simplicity, the existence of an output schema, and the annotations, the description adequately covers the tool's purpose and limitations.

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?

The schema already provides complete description for the single parameter 'name'. The description merely restates its use in the broader context without adding new parameter-level details.

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 provides a free preview of counterparty risk by showing tracked OFAC designations and product recalls. It distinguishes itself from the paid version and sibling tools by specifying its scope.

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 description sets clear context: use for a free preview of specific risk data; for authoritative screening and risk verdict, use the paid tool. It does not explicitly exclude other scenarios but is sufficient.

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

All Signal Oracle tools Inspect

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

A4/5.0

Disambiguation4/5

Most tools target distinct areas (dependency changes, package health, regulatory actions, tariffs, vendor risk), but `preview_feed` is a generic preview that can overlap with the specific preview tools (e.g., `depwatch_preview`), potentially confusing an agent's tool selection.

Naming Consistency3/5

Tool names follow a mix of patterns: most use the suffix `_preview` (e.g., `depwatch_preview`, `regwatch_preview`), but `list_feeds` uses a verb prefix. Additionally, `depwatch` and `tariffwatch` use 'watch' while `packagehealth` does not, introducing inconsistency.

Tool Count5/5

Seven tools is an appropriate number for a monitoring service covering multiple categories (dependencies, health, regulatory, tariffs, vendor risk) without being overwhelming or insufficient.

Completeness2/5

The free tool set only provides previews (up to 5 items) and a listing of feeds, lacking full functionality for detailed queries, history, or actionable results. Users hit a dead end if they need complete data, which is a significant gap.

Resources

Need Help?