DeltaSignal ATLAS-7

DeltaSignal risk distribution

deltasignal_risk_distribution

Read-onlyIdempotent

Use this read-only tool to summarize the active crypto public company universe by ATLAS-7 risk tier. It returns risk-tier buckets such as HIGH, MODERATE, LOW, and UNCLASSIFIED with issuer counts and percentages. Parameters: none; call it exactly as-is when the user asks for market-wide risk mix or high-level distribution. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write external systems or access user accounts. Use it for market-wide context before issuer drilldown; use top_stressed to name the issuers in the high-risk bucket and use issuer tools for company-level analysis.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Risk-tier distribution for the active DeltaSignal issuer universe. Tier names are object keys such as HIGH, MODERATE, LOW, and UNCLASSIFIED.
`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.

Changed11 schema fields changedMay 14, 2026

changedOutput schema / description

Previous value: -"Risk-tier distribution for the active DeltaSignal issuer universe. Tier names are object keys such as HIGH, MODERATE, LOW, and UNCLASSIFIED."New value: +"DeltaSignal ATLAS-7 MCPResponse wrapper. Raw tool payload is returned under data."

removedOutput schema / properties / HIGH

Removed value: -{
-  "additionalProperties": true,
-  "description": "Risk tier bucket.",
-  "properties": {
-    "count": {
-      "description": "Issuer count in this risk tier.",
-      "type": "integer"
-    },
-    "percentage": {
-      "description": "Percentage of the active issuer universe in this tier.",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / LOW

Removed value: -{
-  "additionalProperties": true,
-  "description": "Risk tier bucket.",
-  "properties": {
-    "count": {
-      "description": "Issuer count in this risk tier.",
-      "type": "integer"
-    },
-    "percentage": {
-      "description": "Percentage of the active issuer universe in this tier.",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / MODERATE

Removed value: -{
-  "additionalProperties": true,
-  "description": "Risk tier bucket.",
-  "properties": {
-    "count": {
-      "description": "Issuer count in this risk tier.",
-      "type": "integer"
-    },
-    "percentage": {
-      "description": "Percentage of the active issuer universe in this tier.",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

removedOutput schema / properties / UNCLASSIFIED

Removed value: -{
-  "additionalProperties": true,
-  "description": "Risk tier bucket.",
-  "properties": {
-    "count": {
-      "description": "Issuer count in this risk tier.",
-      "type": "integer"
-    },
-    "percentage": {
-      "description": "Percentage of the active issuer universe in this tier.",
-      "type": "number"
-    }
-  },
-  "type": "object"
-}

addedOutput schema / properties / data

Added value: +{
+  "additionalProperties": true,
+  "description": "Risk-tier distribution for the active DeltaSignal issuer universe. Tier names are object keys such as HIGH, MODERATE, LOW, and UNCLASSIFIED.",
+  "properties": {
+    "HIGH": {
+      "additionalProperties": true,
+      "description": "Risk tier bucket.",
+      "properties": {
+        "count": {
+          "description": "Issuer count in this risk tier.",
+          "type": "integer"
+        },
+        "percentage": {
+          "description": "Percentage of the active issuer universe in this tier.",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "LOW": {
+      "additionalProperties": true,
+      "description": "Risk tier bucket.",
+      "properties": {
+        "count": {
+          "description": "Issuer count in this risk tier.",
+          "type": "integer"
+        },
+        "percentage": {
+          "description": "Percentage of the active issuer universe in this tier.",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "MODERATE": {
+      "additionalProperties": true,
+      "description": "Risk tier bucket.",
+      "properties": {
+        "count": {
+          "description": "Issuer count in this risk tier.",
+          "type": "integer"
+        },
+        "percentage": {
+          "description": "Percentage of the active issuer universe in this tier.",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    },
+    "UNCLASSIFIED": {
+      "additionalProperties": true,
+      "description": "Risk tier bucket.",
+      "properties": {
+        "count": {
+          "description": "Issuer count in this risk tier.",
+          "type": "integer"
+        },
+        "percentage": {
+          "description": "Percentage of the active issuer universe in this tier.",
+          "type": "number"
+        }
+      },
+      "type": "object"
+    }
+  },
+  "required": [],
+  "type": "object"
+}

addedOutput schema / properties / mcp_summary

Added value: +{
+  "description": "Concise high-signal summary of the tool response. Maximum 140 characters.",
+  "type": "string"
+}

addedOutput schema / properties / provenance

Added value: +{
+  "additionalProperties": true,
+  "description": "Traceability information for the MCP tool response.",
+  "properties": {
+    "compacted": {
+      "description": "Whether the data payload was compacted for MCP context safety.",
+      "type": "boolean"
+    },
+    "elapsed_ms": {
+      "description": "Elapsed time for the MCP tool call in milliseconds.",
+      "type": "integer"
+    },
+    "freshness_window_hours": {
+      "description": "Freshness window in hours when reported by the underlying tool.",
+      "type": "integer"
+    },
+    "latest_activity_source_date": {
+      "description": "Latest CompanyFacts activity source date when available.",
+      "examples": [
+        "2026-05-05"
+      ],
+      "format": "date",
+      "maxLength": 10,
+      "minLength": 10,
+      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+      "type": "string"
+    },
+    "latest_computed_source_date": {
+      "description": "Latest computed DeltaSignal source date when available.",
+      "examples": [
+        "2026-05-05"
+      ],
+      "format": "date",
+      "maxLength": 10,
+      "minLength": 10,
+      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+      "type": "string"
+    },
+    "source_date": {
+      "description": "Primary DeltaSignal source date when available.",
+      "examples": [
+        "2026-05-05"
+      ],
+      "format": "date",
+      "maxLength": 10,
+      "minLength": 10,
+      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

addedOutput schema / properties / suggested_follow_ups

Added value: +{
+  "description": "Concrete next MCP calls an agent can run to continue the workflow.",
+  "items": {
+    "additionalProperties": true,
+    "description": "Suggested follow-up MCP call.",
+    "properties": {
+      "args": {
+        "additionalProperties": true,
+        "description": "Arguments for the suggested MCP tool call.",
+        "type": "object"
+      },
+      "tool": {
+        "description": "MCP tool name to call next.",
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / usage_metadata

Added value: +{
+  "additionalProperties": true,
+  "description": "Performance and estimated cost metadata for this MCP tool call.",
+  "properties": {
+    "elapsed_ms": {
+      "description": "Elapsed time for the MCP tool call in milliseconds.",
+      "type": "integer"
+    },
+    "estimated_cost_usd": {
+      "description": "Estimated public x402-equivalent cost in USD when known.",
+      "type": "number"
+    },
+    "tokens_used": {
+      "description": "Token usage when known.",
+      "type": "integer"
+    }
+  },
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[]New value: +[
+  "mcp_summary",
+  "data",
+  "provenance",
+  "suggested_follow_ups"
+]

Changed3 schema fields changedMay 7, 2026

changedOutput schema / description

Previous value: -"Structured JSON result returned by the tool."New value: +"Risk-tier distribution for the active DeltaSignal issuer universe. Tier names are object keys such as HIGH, MODERATE, LOW, and UNCLASSIFIED."

addedOutput schema / properties

Added value: +{
+  "HIGH": {
+    "additionalProperties": true,
+    "description": "Risk tier bucket.",
+    "properties": {
+      "count": {
+        "description": "Issuer count in this risk tier.",
+        "type": "integer"
+      },
+      "percentage": {
+        "description": "Percentage of the active issuer universe in this tier.",
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  "LOW": {
+    "additionalProperties": true,
+    "description": "Risk tier bucket.",
+    "properties": {
+      "count": {
+        "description": "Issuer count in this risk tier.",
+        "type": "integer"
+      },
+      "percentage": {
+        "description": "Percentage of the active issuer universe in this tier.",
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  "MODERATE": {
+    "additionalProperties": true,
+    "description": "Risk tier bucket.",
+    "properties": {
+      "count": {
+        "description": "Issuer count in this risk tier.",
+        "type": "integer"
+      },
+      "percentage": {
+        "description": "Percentage of the active issuer universe in this tier.",
+        "type": "number"
+      }
+    },
+    "type": "object"
+  },
+  "UNCLASSIFIED": {
+    "additionalProperties": true,
+    "description": "Risk tier bucket.",
+    "properties": {
+      "count": {
+        "description": "Issuer count in this risk tier.",
+        "type": "integer"
+      },
+      "percentage": {
+        "description": "Percentage of the active issuer universe in this tier.",
+        "type": "number"
+      }
+    },
+    "type": "object"
+  }
+}

addedOutput schema / required
```
Added value: +[]
```

First observedMay 6, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds specific details: 'performs one HTTPS read, has no destructive side effects, and does not write external systems or access user accounts,' which goes beyond the annotations by describing the exact operational behavior and providing reassurance about external side effects and user data.

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 concise and well-structured: purpose in first clause, output detail, parameters, behavior, and usage alternatives in a logical flow. Each sentence adds value without excess.

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?

With no parameters, an output schema present, and annotations covering safety, the description fully covers what the tool does, when to use it, and how it relates to siblings. The mention of market-wide context and alternatives completes the picture.

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 tool has 0 parameters, and the description explicitly says 'Parameters: none' and 'call it exactly as-is,' which complements the input schema. Since there are no parameters, the description adds minimal but sufficient clarity, meeting the baseline for parameterless tools.

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?

Description clearly states the verb 'summarize' with specific resource (active crypto public company universe by ATLAS-7 risk tier) and output (risk-tier buckets with counts and percentages). It also distinguishes from sibling tools by mentioning top_stressed and issuer tools for drilldown, so a clear differentiation.

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: 'Use it for market-wide context before issuer drilldown; use top_stressed to name the issuers in the high-risk bucket and use issuer tools for company-level analysis.' Also states when to call: 'when the user asks for market-wide risk mix or high-level distribution.'

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?