DeltaSignal ATLAS-7

DeltaSignal public daily brief

deltasignal_public_daily_brief

Read-onlyIdempotent

Use this read-only composite renderer for customer-facing DeltaSignal Daily Brief artifacts. It server-enforces the morning brief evidence plan, then renders a public-safe HTML brief and copy-ready text with plain-English explanations of risk tiers, top-stressed issuers, alpha screens, deltas, and evidence boundaries. Parameters: optional output_mode=compact only; do not pass ticker, limit, offset, source_date, period, or issuer filters because this preset owns exact arguments internally. Behavior: read-only and idempotent; it calls the bounded morning brief composite, has no destructive side effects, removes internal-only identifiers from the public copy, preserves non-advice language, and returns deterministic HTML plus copy_text for publishing workflows. Use it when the user asks for a public daily brief, customer-facing daily brief, investor-ready risk and opportunity scan, or copy-ready DeltaSignal article based on the current daily evidence.

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	Customer-facing DeltaSignal daily brief response. The data object includes rendered HTML, copy_text, public summary fields, term explanations, and a compact evidence boundary.
`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"
+}

AddedMay 27, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description discloses behaviors beyond annotations: it 'server-enforces the morning brief evidence plan,' 'removes internal-only identifiers from the public copy,' 'preserves non-advice language,' and 'returns deterministic HTML plus copy_text.' It also confirms read-only and idempotent behavior, consistent with annotations.

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 structured and front-loaded: purpose, parameters, behavior, and usage. While slightly long, every sentence adds essential information about scope, constraints, and output, with 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?

The description covers purpose, parameters, behavior, output format, and clear usage scenarios. It explains the internal evidence plan enforcement, public-safe rendering, and the exact output fields (HTML and copy_text), making it sufficient for an agent to select and invoke this tool 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% with a clear parameter description ('Only compact is accepted in Phase 1'). The description adds value by explicitly stating 'optional output_mode=compact only' and warning against passing other parameters, reinforcing the schema and clarifying invocation constraints.

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 renderer for customer-facing DeltaSignal Daily Brief artifacts' that renders 'public-safe HTML brief and copy-ready text' with plain-English explanations. It distinguishes itself from siblings by emphasizing the public/customer-facing scope and the composite rendering nature.

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?

Explicit usage guidance is provided: 'Use it when the user asks for a public daily brief, customer-facing daily brief, investor-ready risk and opportunity scan, or copy-ready DeltaSignal article based on the current daily evidence.' It also specifies constraints: 'do not pass ticker, limit, offset, source_date, period, or issuer filters because this preset owns exact arguments internally,' which prevents incorrect invocations.

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?