DeltaSignal ATLAS-7

DeltaSignal morning brief

deltasignal_morning_brief

Read-onlyIdempotent

Use this read-only composite workflow tool as the default first-pass DeltaSignal ATLAS-7 daily scan. It server-enforces the complete morning brief call plan: readiness, daily_changes, risk_distribution, top_stressed with limit 10, alpha_opportunities with limit 10, and alpha_opportunities_audit with limit 10. Parameters: optional output_mode=compact only; do not pass limit, offset, ticker, source_date, or issuer filters because this preset owns exact arguments internally. Behavior: read-only and idempotent; it performs a bounded internal fan-out, has no destructive side effects, and preserves partial results if one required internal call fails. Use it for morning brief, daily brief, daily scan, current risk board, and newsroom first-pass requests; sell company-report or deep-brief issuer reports separately when the user wants drilldown explanation.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`output_mode`	No	Optional response mode. Only compact is accepted in Phase 1.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Server-enforced DeltaSignal morning brief composite response. The data object preserves successful subtool payloads plus a deterministic internal call ledger.
`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.

Changed4 schema fields changedJun 9, 2026

removedOutput schema / properties / data / properties / evidence_sections

Removed value: -{
-  "description": "Company-report section availability records. States include available, soft_miss, not_requested, failed_advisory, and failed_closed.",
-  "items": {
-    "additionalProperties": true,
-    "description": "Evidence section availability record.",
-    "type": "object"
-  },
-  "type": "array"
-}

removedOutput schema / properties / data / properties / issuer_evidence_envelope

Removed value: -{
-  "additionalProperties": true,
-  "description": "Company-report evidence envelope with parser-stable sections, availability states, SPECTRA metadata, and non-advice boundary.",
-  "type": "object"
-}

removedOutput schema / properties / data / properties / publication_audit_block

Removed value: -{
-  "additionalProperties": true,
-  "description": "Compact audit block for report publication, including route, evidence hash, section availability summary, SPECTRA state, and daily-change drilldown reference.",
-  "type": "object"
-}

removedOutput schema / properties / data / properties / spectra_metadata

Removed value: -{
-  "additionalProperties": true,
-  "description": "Promoted SPECTRA metadata for company reports, including latest point dates, row counts, current read, risk tier, charge level, and source date bounds when available.",
-  "type": "object"
-}

Changed4 schema fields changedJun 8, 2026

addedOutput schema / properties / data / properties / evidence_sections

Added value: +{
+  "description": "Company-report section availability records. States include available, soft_miss, not_requested, failed_advisory, and failed_closed.",
+  "items": {
+    "additionalProperties": true,
+    "description": "Evidence section availability record.",
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / issuer_evidence_envelope

Added value: +{
+  "additionalProperties": true,
+  "description": "Company-report evidence envelope with parser-stable sections, availability states, SPECTRA metadata, and non-advice boundary.",
+  "type": "object"
+}

addedOutput schema / properties / data / properties / publication_audit_block

Added value: +{
+  "additionalProperties": true,
+  "description": "Compact audit block for report publication, including route, evidence hash, section availability summary, SPECTRA state, and daily-change drilldown reference.",
+  "type": "object"
+}

addedOutput schema / properties / data / properties / spectra_metadata

Added value: +{
+  "additionalProperties": true,
+  "description": "Promoted SPECTRA metadata for company reports, including latest point dates, row counts, current read, risk tier, charge level, and source date bounds when available.",
+  "type": "object"
+}

Changed2 schema fields changedMay 27, 2026

changedOutput schema / properties / data / properties / issuer_drilldown_policy / description

Previous value: -"Morning-brief ticker selection and advisory issuer-layer policy for fundamentals, stress, peer, alpha, and SPECTRA evidence."New value: +"Morning-brief issuer drilldown policy. Standard morning briefs do not run advisory issuer layers automatically; use company-report or deep-brief follow-ups for fundamentals, stress, peer, alpha, and SPECTRA evidence."

changedOutput schema / properties / data / properties / issuer_drilldowns / description

Previous value: -"Bounded issuer evidence groups selected from the daily scan. Each group can include company_fundamentals, covenant_stress, peer_ranking, alpha_signals, and spectra_field_map payloads."New value: +"Reserved issuer evidence groups. Empty for standard morning briefs unless a future explicit deep-brief mode runs issuer drilldowns."

Changed2 schema fields changedMay 16, 2026

addedOutput schema / properties / data / properties / issuer_drilldown_policy

Added value: +{
+  "additionalProperties": true,
+  "description": "Morning-brief ticker selection and advisory issuer-layer policy for fundamentals, stress, peer, alpha, and SPECTRA evidence.",
+  "type": "object"
+}

addedOutput schema / properties / data / properties / issuer_drilldowns

Added value: +{
+  "description": "Bounded issuer evidence groups selected from the daily scan. Each group can include company_fundamentals, covenant_stress, peer_ranking, alpha_signals, and spectra_field_map payloads.",
+  "items": {
+    "additionalProperties": true,
+    "description": "Issuer drilldown evidence group.",
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedMay 14, 2026

addedOutput schema / properties / data / properties / spectra_field_map

Added value: +{
+  "additionalProperties": true,
+  "description": "Raw deltasignal_spectra_field_map payload when a company-report SPECTRA advisory leg succeeds.",
+  "type": "object"
+}

AddedMay 14, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive, but the description adds concrete behavioral details: server-enforces the full call plan, performs a bounded internal fan-out, preserves partial results if a required internal call fails, and only accepts compact output mode. This goes well beyond annotations and gives the agent accurate expectations.

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 dense but efficiently organized: purpose, call plan, parameter constraints, behavioral guarantees, and usage scope in a logical flow. Every sentence provides necessary information, though the length is slightly higher than minimal due to the composite nature of the tool. It remains well-structured and front-loaded.

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 composite complexity, the presence of an output schema, and strong annotations, the description is remarkably complete. It covers invocation semantics, internal call composition, failure behavior, accepted output mode, and alternative tools for drilldown, leaving no significant gaps for an agent to resolve.

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?

The single parameter output_mode is fully described in the schema (and the description confirms it), but the description adds crucial extra semantics by explicitly listing parameters that must NOT be passed (limit, offset, ticker, source_date, issuer filters) because the preset owns those internally. This prevents misuse that schema alone wouldn't catch.

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 is a read-only composite workflow tool for a daily scan, enumerates the exact internal call plan (readiness, daily_changes, risk_distribution, top_stressed, etc.) with limits, and distinguishes it from company-report or deep-brief drilldown tools. This is specific, action-oriented, and differentiates it from the extensive sibling list.

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 instructs when to use it ('morning brief, daily brief, daily scan, current risk board, newsroom first-pass requests') and when not to ('sell company-report or deep-brief issuer reports separately for drilldown'). Also warns against passing conflicting parameters like limit or ticker, which is essential for correct invocation.

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?