Skip to main content
Glama

DeltaSignal ATLAS-7

by io.github.aitrailblazer

DeltaSignal Synthetic ETF audit payload

deltasignal_synthetic_etf_audit
Read-onlyIdempotent

Use this read-only audit tool when the user asks what factors drive the Delta Signal Synthetic AI 10 ETF state, asks for raw audit evidence, or asks whether the current pressure state is a full four-level ATLAS-7 verdict. It returns current and previous buckets, bucket comparison, factor-history rows, audit-window z-scores including basis_pressure_z, a threshold contract, threshold flags, canonical event status/reasons/blockers, event classification, four-level coverage, bounded constituent contribution rows, presentation-parity status, TRIDENT/liquidation-gradient availability, per-question readiness, provenance, caveats, and quality flags. Parameters: product is required and accepts AI10, Synthetic AI10 ETF, AI-PERP-INTX, Tech100, or TEK-19DEC30-CDE; optional source-date filters override window_days; optional limit and offset paginate factor-history rows. Behavior: read-only and idempotent with no destructive side effects; it must label partial coverage explicitly and must not convert a linked-market read into issuer truth, exchange-native microstructure truth, a trade signal, or investment advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum factor-history rows to return. Defaults to 100 and is capped at 100 through MCP.
offsetNoPagination offset over factor-history rows used for audit.
productYesRequired Synthetic ETF or linked product identifier, for example AI10, Synthetic AI10 ETF, or AI-PERP-INTX.
source_dateNoOptional exact source date in YYYY-MM-DD format. Overrides window_days.
window_daysNoDefault audit lookback when no source-date filters are supplied. Defaults to 7 and is capped at 30.
include_exportNoWhether to include export availability metadata. Defaults true.
source_date_toNoOptional inclusive source-date upper bound in YYYY-MM-DD format.
source_date_fromNoOptional inclusive source-date lower bound in YYYY-MM-DD format.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesAudit-grade DeltaSignal Synthetic ETF payload.
provenanceYesTraceability information for the MCP tool response.
mcp_summaryYesConcise high-signal summary of the tool response. Maximum 140 characters.
usage_metadataNoPerformance and estimated cost metadata for this MCP tool call.
suggested_follow_upsYesConcrete next MCP calls an agent can run to continue the workflow.

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds crucial context beyond that: 'must label partial coverage explicitly' and 'must not convert a linked-market read into issuer truth, exchange-native microstructure truth, a trade signal, or investment advice'. This is meaningful behavioral disclosure that the agent needs for safe invocation.

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 front-loaded with the core usage, then lists return contents, parameters, and behavior in a readable order. The long list of returned fields is somewhat dense but each item is specific and necessary to convey scope. No wasted words.

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 complexity (8 parameters, output schema, many siblings), this description is exceptionally complete. It covers purpose, usage triggers, return contents, parameter semantics, and behavioral caveats. The output schema exists so not detailing every field is acceptable.

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 extra value by noting product accepted values (AI10, Synthetic AI10 ETF, AI-PERP-INTX, etc.), the override relationship between source-date filters and window_days, and the pagination purpose of limit/offset. This synthesis goes beyond what the schema provides.

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?

Description opens with a specific verb+resource+scope: 'read-only audit tool' for 'Delta Signal Synthetic AI 10 ETF state', and enumerates exact triggers (factor drivers, raw audit evidence, four-level ATLAS-7 verdict). This clearly distinguishes it from siblings like deltasignal_synthetic_etf_pressure_state and other audit tools.

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?

It provides explicit 'when to use' conditions: 'when the user asks what factors drive...' and 'when the user asks whether the current pressure state is a full four-level ATLAS-7 verdict'. While it doesn't name alternative tools for exclusion, the context is clear enough that an agent can decide appropriately.

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

All DeltaSignal ATLAS-7 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

C2.8/5.0
Disambiguation2/5

The tool set has extensive overlap: natural-language variants duplicate raw JSON tools (e.g., deltasignal_covenant_stress vs deltasignal_covenant_stress_natural), composite workflow tools duplicate low-level screens (deltasignal_alpha_sweep vs deltasignal_alpha_opportunities), and the atlas7_* and deltasignal_* prefixes repeat the same concepts (e.g., atlas7_covenant_stress vs deltasignal_covenant_stress). An agent would likely struggle to pick the right tool for a given intent.

Naming Consistency2/5

Three distinct prefixes (atlas7_, deltasignal_, strategix_) are used, and duplicate tool names appear across prefixes (e.g., atlas7_readiness vs deltasignal_readiness). Verb patterns are inconsistent, mixing nouns and verbs (atlas7_archive_search, deltasignal_thesis_create, deltasignal_morning_brief_natural), and there is no clear rule for raw, natural, composite, or resolver variants.

Tool Count1/5

With 81 tools, the server is massively over-scoped. Many are near-duplicates or overlapping composites; the core domain likely needs 20-30 tools at most. The count is far beyond what an agent can reasonably navigate, and it indicates a failure to consolidate or version the surface.

Completeness3/5

The set covers a broad range of functionality: screening, stress, alpha, peer comparison, history, tripcode resolution, synthetic ETF state, and thesis monitoring. However, there are lifecycle gaps (e.g., thesis_create has no corresponding update/delete, and the atlas7 vs deltasignal split leaves no unified surface). The duplication suggests comprehensive coverage in some areas and awkward holes in others.

Resources