DeltaSignal ATLAS-7

DeltaSignal pressure board

deltasignal_pressure_board

Read-onlyIdempotent

Use this read-only composite workflow tool for risk and stress monitoring across the current DeltaSignal issuer universe. It server-enforces the pressure-board call plan: readiness, top_stressed with limit 15, and risk_distribution. 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 three internal HTTPS reads, has no destructive side effects, never calls issuer-level tools, and preserves partial results if one internal call fails. Use it when the user asks for risk monitoring, pressure board, stress board, top stressed overview, or current risk mix.

Input Schema

TableJSON Schema

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

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Server-enforced DeltaSignal pressure board 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.9/5.0

Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint), the description adds meaningful behavioral detail: three internal HTTPS reads, preservation of partial results if one call fails, no calls to issuer-level tools, and no destructive side effects. This enriches the agent's understanding of what happens at runtime without contradicting annotations.

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?

Five sentences, logically organized into purpose, call plan, parameters, behavior, and usage triggers. Every sentence contributes essential information with no redundancy or fluff. The structure is front-loaded with the core purpose before diving into details.

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?

For a composite workflow tool with one optional parameter and existing output schema, the description covers all critical aspects: exact internal operations, parameter restrictions, behavioral characteristics, and user-intent triggers. With annotations and output schema handling safety and return values, this is complete.

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 fully covers output_mode with a description ('Only compact is accepted'), so the baseline is 3. The tool description adds value by reiterating the constraint and explaining why other parameters are not allowed ('this preset owns exact arguments internally'), preventing the agent from attempting unsupported filters. The schema coverage is 100% and the extra contextual rationale justifies a 4.

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 composite workflow for risk and stress monitoring across the DeltaSignal issuer universe, and explicitly enumerates the server-enforced call plan (readiness, top_stressed with limit 15, risk_distribution). This distinguishes it from individual sibling tools like deltasignal_top_stressed or deltasignal_risk_distribution by presenting it as a preset orchestration.

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?

Provides explicit usage triggers ('when the user asks for risk monitoring, pressure board, stress board, top stressed overview, or current risk mix') and explicitly tells the agent not to pass limit, offset, ticker, source_date, or issuer filters because the preset owns arguments. This gives clear situational guidance and implicitly points to finer-grained alternatives.

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?