DeltaSignal ATLAS-7

DeltaSignal company report

deltasignal_company_report

Read-onlyIdempotent

Use this read-only composite workflow tool for the default full single-issuer DeltaSignal ATLAS-7 company report add-on. It server-enforces the complete company report call plan: readiness, company_fundamentals, alpha_signals, peer_ranking, covenant_stress, and SPECTRA field-map support for one normalized ticker. Parameters: ticker is required and normalized to uppercase; period, include_segments, include_related_party, and output_mode=compact are optional. SPECTRA is included when a field-map contract is available for the issuer. Behavior: read-only and idempotent; it performs six internal HTTPS reads, has no destructive side effects, rejects invalid tickers before fan-out, and preserves partial results if a required issuer leg fails. Use it when the user asks for a report, deep dive, issuer brief, or diligence package on one crypto public-company ticker, or when a Morning Brief top-stressed or alpha-screen row needs a separately sold explanation report; use low-level tools only for custom drilldowns.

Input Schema

TableJSON Schema

Name	Required	Description
`period`	No	Optional YYYY-MM-DD reporting period to pass to fundamentals, peer ranking, and covenant stress when reproducing a known filing date.
`ticker`	Yes	Required crypto public company ticker. The server trims whitespace and normalizes to uppercase before all internal calls. Examples: RIOT, MARA, COIN, MSTR.
`output_mode`	No	Optional response mode. Only compact is accepted in Phase 1.
`include_segments`	No	Request segment containers from company_fundamentals when available.
`include_related_party`	No	Request related-party containers from company_fundamentals when available.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Server-enforced DeltaSignal company report composite response.
`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?

Even though annotations already provide readOnlyHint, idempotentHint, and destructiveHint, the description adds valuable context: 'performs six internal HTTPS reads, has no destructive side effects, rejects invalid tickers before fan-out, and preserves partial results if a required issuer leg fails.' It also clarifies SPECTRA inclusion logic, which goes beyond the 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 longer than average but appropriately so for a composite workflow. It is front-loaded with the core purpose, then covers parameters, behavior, and usage in a logical sequence. Each sentence provides specific information; 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, the presence of an output schema (so return values need not be explained), and rich annotations, the description is complete. It covers purpose, parameter semantics, internal behavior, error handling, partial results, and use cases. The agent has all necessary context to 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?

The schema already has 100% coverage with descriptions for each parameter. The tool description adds extra meaning by explaining that period is passed to fundamentals, peer ranking, and covenant stress, and that include_segments/include_related_party request containers from company_fundamentals. This enhances the schema without being redundant.

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 this is a read-only composite workflow tool for the default full single-issuer DeltaSignal ATLAS-7 company report. It enumerates the included components (readiness, company_fundamentals, alpha_signals, etc.) and explicitly contrasts with low-level tools for custom drilldowns, making it distinguishable from sibling tools.

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?

The description provides explicit when-to-use guidance: 'Use it when the user asks for a report, deep dive, issuer brief, or diligence package on one crypto public-company ticker, or when a Morning Brief top-stressed or alpha-screen row needs a separately sold explanation report.' It also states the alternative: 'use low-level tools only for custom drilldowns.' This clearly orients the agent.

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?