Skip to main content
Glama

sygnldata — market intelligence for trading agents

by com.sygnliq

sygnl47_subscribe_live_24h

Buy a 24-hour unmetered pass to the SYGNL/47 live tier ($50.00).

RETURNS: {token, sub_id, tier, expires_utc, max_freshness_seconds, authorized_routes}. Send the token as header X-SYGNL47-TOKEN on any authorized route and no per-call payment is charged until it expires. STORE THE TOKEN — verification is stateless by design, so we cannot reissue it. WHAT IT DOES NOT BUY: fresher data. The pass grants unmetered access to the live tier, and the server-side ts_utc cutoff applies to pass holders exactly as it does to per-call buyers. An expired token falls back to a normal 402 challenge, never to a free serve. PRICE: $50.00 USDC, versus $2.00 per live call. NOT A PREDICTION: this buys access to a verified observation feed with zero confirmed live outcomes, whose current inventory is 2 replay-sourced events.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
payment_signatureNo

TDQS

A4.4/5.0
Behavior5/5

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

No annotations are provided, so the description fully carries the behavioral disclosure burden. It details the mutation (buying a pass), stateless verification, token usage, return fields, pricing, and current inventory, leaving no ambiguity.

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 well-structured with the core action first, followed by returns, caveats, pricing, and clarifications. It is appropriately front-loaded but slightly verbose with additional clarifications that could be condensed.

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?

Despite no output schema, the description provides detailed return fields and behavioral context. It covers pricing, token usage, fallback, and limitations. However, it lacks prerequisites or instructions for obtaining the payment signature.

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

Parameters2/5

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

Only one parameter (payment_signature) with zero schema description coverage. The description does not explain its format, how to obtain it, or its significance; it only appears in the schema with a default empty string.

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 buys a 24-hour unmetered pass to the SYGNL/47 live tier for $50.00. It distinguishes from sibling subscription tools and per-call alternatives, and lists return fields.

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?

Explicitly compares to per-call pricing ($2.00 per live call), clarifies what the pass does not buy (fresher data), explains token storage and fallback behavior, and warns it is not a prediction.

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 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.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