Signal Oracle

Preview any feed

preview_feed

Read-only

Free preview (up to 5 recent changes) for any feed. Pass the feed's source slug (from list_feeds). Optionally: since (ISO-8601) to window; scope to filter to an entity-id prefix on feeds that support it (e.g. an HTS code); or package/repo/ecosystem on feeds that resolve arbitrary entities live (e.g. dependency feeds). The full feed, status, and LLM brief are paid via x402.

Input Schema

TableJSON Schema

Name	Required	Description
`repo`	No	GitHub owner/repo for dependency feeds
`scope`	No	Entity-id prefix filter for feeds that declare a scope param
`since`	No	ISO-8601 instant; only changes detected after this
`source`	Yes	Feed source slug, e.g. 'depwatch' or 'cve' (see list_feeds)
`package`	No	Package name for dependency feeds (resolved live)
`ecosystem`	No	Registry hint, e.g. 'npm' or 'pypi'

Output Schema

TableJSON Schema

Name	Required	Description	Default
`url`	No
`hint`	No
`note`	No
`tier`	No
`error`	No
`price`	No
`entity`	No
`params`	No
`source`	No
`changes`	No
`upgrade`	No
`question`	No
`freeTeaser`	No
`previewCount`	No
`exampleRequest`	No

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=true. The description adds context: the free preview returns up to 5 recent changes, the full feed is paid via x402, and optional parameters modify behavior. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single but dense sentence using semicolons to separate clauses. It packs all necessary information without unnecessary words. Slightly long but efficient.

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?

Given the output schema exists (not shown but present) and schema coverage is 100%, the description covers all key aspects: free preview limits, parameter purposes, and the paid model. It is complete for a preview tool with these annotations.

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 significant meaning beyond schema descriptions: it explains source comes from list_feeds, scope is an entity-id prefix, and package/repo/ecosystem are for dependency feeds. This helps the agent understand when and how to use each parameter.

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 it's a free preview of up to 5 recent changes for any feed, with a specific verb ('preview') and resource ('feed'). It distinguishes from sibling tools by being a generic preview that takes a source slug, while siblings are specific feed previews.

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 explains to pass the feed's source slug from list_feeds and describes optional parameters and their use cases (e.g., 'since' for time window, 'scope' for entity-id filter). It mentions the full feed is paid, implying when not to use it. However, it does not explicitly compare with sibling tools.

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?