sygnldata — market intelligence for trading agents

sygnl47_entities

Tracked entity gazetteer plus today's guard state ($0.25).

RETURNS: every entity SYGNL/47 listens for with its disambiguation rules attached — a country only counts when a policy instrument is nearby, "intel" does not count next to "agency", "apple" does not count next to "pie" — and, per ticker, whether it is BLOCKED right now by the earnings and liquidity guards, with the reason string. WHY IT CHANGES: a name being watched and a name being actionable today are different facts. An earnings print inside the holding window destroys move attribution, so those names are refused outright. Liquidity below $10M 20-session average dollar volume is a hard reject. A guard that could not check reports UNKNOWN and never silently passes. GUARANTEED MAX STALENESS: guard state is resolved at publish time; the response carries guards_evaluated_utc and sync.feed_age_seconds so you can judge it yourself. PRICE: $0.25 USDC. NOT A PREDICTION: this is a reference and constraint dataset, not a recommendation to trade any name it lists as allowed.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`payment_signature`	No

TDQS

A3.5/5.0

Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: returns disambiguation rules, guard state with reasons, explains why state changes (earnings prints, liquidity), guarantees staleness with timestamps, and states pricing. Very transparent.

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

Conciseness3/5

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

The description is verbose but well-structured with labeled sections. However, it could be more concise while retaining all key information.

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 low complexity (1 parameter, no output schema, no annotations), the description is rich in behavioral details. However, missing parameter explanation and usage guidance prevent higher score.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The only parameter, 'payment_signature', has no description in the schema (0% coverage) and the tool description does not explain its purpose or usage. The mention of '$0.25 USDC' does not clarify the parameter role.

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 that the tool returns a 'tracked entity gazetteer plus today's guard state', with specific disambiguation rules and per-ticker BLOCKED status. This distinguishes it from sibling tools that focus on events or pricing.

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

Usage Guidelines2/5

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

The description does not provide guidance on when to use this tool versus its siblings. It includes a disclaimer 'NOT A PREDICTION' but no explicit comparison or context for selection.

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

All sygnldata — market intelligence for trading agents 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

A3.7/5.0

Disambiguation5/5

Each tool has a distinct purpose, with clear differentiation between SYGNL/47 event tiers (live, 1m, 15m, archive), subscription management, and auxiliary tools like backtesting and regime detection. No overlapping functionality.

Naming Consistency4/5

Most tools follow a descriptive underscore pattern, with 'sygnl47_' prefix for event and subscription tools, and 'get_' for data retrieval. Some variation in verb prefixes (audit, check, estimate) but overall predictable and readable.

Tool Count4/5

21 tools is slightly high but justified by the tiered data access model for SYGNL/47 events and supporting infrastructure. The count covers core functionality without being excessive.

Completeness4/5

The tool set covers the stated domain well: event monitoring at different recency, backtesting, regime detection, and subscription management. Minor gaps like historical pricing data are not central to the server's focus.

Resources

Need Help?