DeltaSignal ATLAS-7

DeltaSignal quick ticker check

deltasignal_quick_ticker_check

Read-onlyIdempotent

Use this read-only composite workflow tool for a fast single-ticker sanity check without the full company-report payload. It server-enforces the quick-check call plan: readiness, covenant_stress, and alpha_signals for one normalized ticker. Parameters: ticker is required and normalized to uppercase; output_mode=compact is optional. Fundamentals, peer ranking, and SPECTRA are intentionally excluded. Behavior: read-only and idempotent; it performs three 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 whether one ticker is clean, stressed, actionable, or needs deeper diligence.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`ticker`	Yes	Required crypto public company ticker. The server trims whitespace and normalizes to uppercase before all internal calls.
`output_mode`	No	Optional response mode. Only compact is accepted.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Server-enforced DeltaSignal quick ticker check 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.5/5.0

Behavior5/5

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

Despite strong annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds valuable behavioral detail beyond them: it performs three internal HTTPS reads, rejects invalid tickers before fan-out, preserves partial results if an issuer leg fails, and has no destructive side effects. This gives the agent a precise operational model.

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 a single, logically organized paragraph that front-loads the core purpose and then adds necessary detail. Every sentence serves a purpose—delimiting scope, listing components, explaining exclusions, and stating behavior—with no fluff 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?

Given the tool's composite nature, the description covers purpose, usage, exclusions, parameter behavior, safety, and failure semantics. With an output schema present, it does not need to describe return values, and the annotations already declare safety, so the description is complete for an agent to select and invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The schema already documents both parameters with 100% coverage, including ticker normalization and output_mode constraints. The description echoes these facts (e.g., 'ticker is required and normalized to uppercase') but does not add significant new meaning 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 clearly states the tool is a read-only composite workflow for a fast single-ticker sanity check, listing the exact sub-calls (readiness, covenant_stress, alpha_signals) and explicitly noting it excludes the full company-report payload. This distinguishes it from sibling tools like the full company report or deeper diligence 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 provides clear use-case guidance: 'Use it when the user asks whether one ticker is clean, stressed, actionable, or needs deeper diligence.' It also states exclusions (fundamentals, peer ranking, SPECTRA) and contrasts with the full report, though it does not name specific alternative sibling tools.

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.

TDQS

B3.1/5.0

Disambiguation2/5

Significant overlap exists between atlas7_* and deltasignal_* tools for the same concepts (covenant stress, readiness, peer ranking, morning brief, pressure board), and composite workflows coexist with their low-level components. The descriptions are detailed but the sheer number of similar-scope tools makes misselection likely.

Naming Consistency4/5

Most tools follow a consistent lower_snake_case pattern with a domain prefix (atlas7_, deltasignal_, strategix_). Verb-first names (generate_, resolve_, search_) and noun-only names (alpha_opportunities, readiness) are both used, but the convention is predictable enough to navigate.

Tool Count1/5

With 81 tools, the surface is far beyond the 25–50 range considered excessive. Many tools are composites, natural-language variants, or near-duplicates that could be consolidated, creating an extreme mismatch for typical MCP server scope.

Completeness4/5

The tool surface is extensive, covering fundamentals, covenant stress, alpha screening, peer ranking, daily changes, briefs, historical ATLAS data, TripCode resolution, perp factors, synthetic ETF audit, and StrategiX rendering. Minor gaps exist (watchlist persistence, thesis lifecycle), but core research workflows are well covered.

Resources

Need Help?