DeltaSignal ATLAS-7

DeltaSignal Synthetic ETF pressure state

deltasignal_synthetic_etf_pressure_state

Read-onlyIdempotent

Use this read-only composite tool when the user asks for the current pressure state of the Delta Signal Synthetic AI 10 ETF or Synthetic Tech100 ETF. It returns one user-facing pressure-state envelope assembled from persisted constituent registry evidence and persisted market-factor/SPECTRA history. Parameters: product is required and accepts AI10, Synthetic AI10 ETF, AI-PERP-INTX, Tech100, or TEK-19DEC30-CDE; optional source date filters, limit, and offset constrain the factor-history window. Behavior: read-only and idempotent with no destructive side effects; it does not fetch live exchange state, expose provider branding outside bounded identity lineage, place trades, or mutate recorder state.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum factor-history points to inspect before building the pressure state. Defaults to 10 and is capped at 100 through MCP.
`offset`	No	Pagination offset over factor-history points used for the pressure state.
`product`	Yes	Required Synthetic ETF or linked product identifier, for example AI10, Synthetic AI10 ETF, or AI-PERP-INTX.
`source_date`	No	Optional exact source date in YYYY-MM-DD format.
`source_date_to`	No	Optional inclusive source-date upper bound in YYYY-MM-DD format.
`source_date_from`	No	Optional inclusive source-date lower bound in YYYY-MM-DD format.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Composite DeltaSignal Synthetic ETF pressure-state envelope.
`provenance`	Yes	Traceability information for the MCP tool response.
`mcp_summary`	Yes	Concise high-signal summary of the tool response. Maximum 140 characters.
`usage_metadata`	No	Performance and estimated cost metadata for this MCP tool call.
`suggested_follow_ups`	Yes	Concrete next MCP calls an agent can run to continue the workflow.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed7 schema fields changedJun 28, 2026

addedOutput schema / properties / data / properties / caveats

Added value: +{
+  "description": "Top-level caveats for client display and contract validation.",
+  "items": {
+    "description": "Caveat sentence.",
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / computed_at_utc

Added value: +{
+  "description": "UTC computation timestamp from the preserved factor row quality envelope.",
+  "examples": [
+    "2026-05-05T23:02:17Z"
+  ],
+  "format": "date-time",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / evidence_hash

Added value: +{
+  "description": "Evidence hash preserved from the factor row lineage or quality envelope.",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / observed_bucket_utc

Added value: +{
+  "description": "UTC observed bucket represented by the pressure-state factor row.",
+  "examples": [
+    "2026-05-05T23:02:17Z"
+  ],
+  "format": "date-time",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / quality_flags

Added value: +{
+  "description": "Top-level quality flags mirrored from data_quality_warnings for client validation.",
+  "items": {
+    "description": "Quality flag.",
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / route_uri

Added value: +{
+  "description": "Canonical REST route URI template used by the MCP tool.",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / source_date

Added value: +{
+  "description": "Latest source date represented by the pressure-state factor row.",
+  "examples": [
+    "2026-05-05"
+  ],
+  "format": "date",
+  "maxLength": 10,
+  "minLength": 10,
+  "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+  "type": "string"
+}

Changed3 schema fields changedJun 28, 2026

addedOutput schema / properties / data / properties / disclosures

Added value: +{
+  "description": "Synthetic benchmark and non-advice disclosures.",
+  "items": {
+    "description": "Disclosure sentence.",
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / identity_lineage

Added value: +{
+  "additionalProperties": true,
+  "description": "Canonical synthetic benchmark identity, legacy alias migration metadata, method continuity, and evidence-role boundary.",
+  "type": "object"
+}

changedOutput schema / properties / data / required

Previous value: -[
-  "display_name",
-  "pressure_state",
-  "evidence_boundary"
-]New value: +[
+  "display_name",
+  "identity_lineage",
+  "pressure_state",
+  "evidence_boundary"
+]

AddedJun 28, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds valuable context: it is a 'composite tool' using persisted evidence, and explicitly lists non-behaviors (no live fetch, no trades, no recorder mutation). This goes well beyond the structured hints and informs the agent about limitations that are not otherwise visible.

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?

The description is compact (three sentences) and well-structured: trigger and output first, parameter overview second, behavioral caveats last. Every clause earns its place; no filler or redundancy.

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?

With a rich output schema present, the description need not explain return values, and it does not. It covers what the tool does, when to use it, key parameters, and behavioral boundaries, which is sufficient for an agent to select and invoke it correctly.

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 a baseline of 3 applies, but the description adds meaningful value by enumerating the accepted product values (including 'Tech100' and 'TEK-19DEC30-CDE' not in schema examples) and by explaining that date filters and limit/offset constrain the factor-history window. This contextual hand-holding raises it above baseline.

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 opens with a specific trigger ('when the user asks for the current pressure state of the Delta Signal Synthetic AI 10 ETF or Synthetic Tech100 ETF') and clearly names the resource and action. It distinguishes itself from siblings by focusing narrowly on the synthetic ETF pressure state and listing exact product identifiers, avoiding overlap with general pressure board or market context 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 explicitly states the usage context in the first sentence ('Use this read-only composite tool when...'), which is clear and actionable. It also provides exclusions ('does not fetch live exchange state, place trades, or mutate recorder state'), but does not name alternative tools for those cases, so it falls short of a full 5.

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

Resources

Need Help?