DeltaSignal ATLAS-7

DeltaSignal Morning Brief Natural Language brief

deltasignal_morning_brief_natural

Read-onlyIdempotent

Use this premium read-only Natural Language tool when the user wants the server-composed Morning Brief rendered as audit-grade Markdown. It compiles backend-composed compact evidence across readiness, daily changes, risk distribution, top stressed issuers, and alpha opportunities. The renderer never fans out into tools and never generates social drafts or trade recommendations. Parameters: style is professional, concise, trader, or detailed. Date and limit are accepted only where the backend composite supports them. Behavior: read-only and idempotent; it performs the server-enforced Morning Brief workflow, has no destructive side effects, then renders the returned compact evidence as a bounded Natural Language response.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Optional compact record limit where supported.
`style`	No	Rendering style. Style changes tone and density only, not facts.
`period`	No	Optional YYYY-MM-DD date selector when supported by the backend composite.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Natural Language Morning Brief response rendered from backend-composed compact evidence.
`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.6/5.0

Behavior5/5

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

Annotations already state readOnly, idempotent, and non-destructive. The description adds substantial behavioral context: it 'compiles backend-composed compact evidence', 'performs the server-enforced Morning Brief workflow', 'never fans out into tools', and 'renders... as a bounded Natural Language response.' These traits are not inferable from annotations alone and provide clear 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 slightly long but well-organized: it front-loads the core purpose, then describes compilation, exclusions, parameters, and behavior in logical order. Each sentence contributes unique information, though the parameter list could be trimmed slightly without losing meaning.

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 moderate complexity, rich annotations, and existing output schema, the description covers purpose, content scope, exclusions, parameter caveats, and behavioral guarantees. It does not need to cover return values because the output schema exists. The inclusion of 'never generates social drafts or trade recommendations' also contextualizes against sibling tools.

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% with detailed parameter descriptions. The description adds value by noting that 'Date and limit are accepted only where the backend composite supports them,' which is a conditional not in the schema. It also restates the style enum values but does not introduce new semantics for the parameters beyond the schema.

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 starts with a clear verb and resource: 'Use this premium read-only Natural Language tool when the user wants the server-composed Morning Brief rendered as audit-grade Markdown.' It specifies the output format (Markdown), the content categories (readiness, daily changes, etc.), and explicitly distinguishes itself from siblings by noting it never fans out into tools or generates drafts/recommendations.

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?

The description gives a clear when-to-use condition ('when the user wants... rendered as audit-grade Markdown') and exclusions ('never fans out into tools', 'never generates social drafts or trade recommendations'). It also provides conditional parameter guidance ('accepted only where the backend composite supports them'). However, it does not explicitly name alternative sibling tools for comparison, so it stops short of full alternatives guidance.

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?