DeltaSignal ATLAS-7

DeltaSignal alpha opportunities

deltasignal_alpha_opportunities

Read-onlyIdempotent

Use this read-only screening tool to rank the active DeltaSignal issuer universe by deterministic Phase 1 alpha score. It returns opportunity rows with ticker, CIK/entity metadata when available, issuer type, raw alpha score, board rank score, risk tier, debt coverage, quality, treasury, regime, and provenance fields. Parameters: limit is 1-100; source_date replays a known YYYY-MM-DD slice; risk_tier, quality_flag, issuer_type, include_funds, and debt_coverage_status narrow the screen. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not handle wallets, payments, orders, or account state. Default behavior returns operating-company issuers. Use include_funds=true or issuer_type=etf_trust|fund_vehicle|all only when the user asks for ETF, trust, fund, or product-vehicle screens. High scores are drilldown candidates, not standalone conclusions.

Input Schema

TableJSON Schema

Name	Required	Description
`limit`	No	Maximum rows to return. Use 10-25 for agent summaries and up to 100 for full screening.
`risk_tier`	No	Optional risk tier filter such as HIGH, MODERATE, LOW, or UNCLASSIFIED.
`issuer_type`	No	Optional issuer-type filter: operating_company, etf_trust, fund_vehicle, foreign_issuer, unresolved_identifier, or all.
`source_date`	No	Optional DeltaSignal source slice date in YYYY-MM-DD format.
`quality_flag`	No	Optional normalized quality filter such as high, medium, low, or unknown.
`include_funds`	No	Set true to include ETF, trust, fund, and product-vehicle rows in the screen.
`debt_coverage_status`	No	Optional debt coverage filter such as resolved_nonzero, legitimate_zero_debt, or low_confidence_missing_debt.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Ranked Phase 1 alpha-opportunity screen for the active DeltaSignal issuer universe. The default screen focuses on operating-company issuers and requires issuer drilldown; ETF/trust/fund/product vehicles require explicit opt-in.
`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.

Changed16 schema fields changedMay 14, 2026

addedInput schema / properties / include_funds

Added value: +{
+  "description": "Set true to include ETF, trust, fund, and product-vehicle rows in the screen.",
+  "type": "boolean"
+}

addedInput schema / properties / issuer_type

Added value: +{
+  "description": "Optional issuer-type filter: operating_company, etf_trust, fund_vehicle, foreign_issuer, unresolved_identifier, or all.",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}

addedInput schema / properties / quality_flag

Added value: +{
+  "description": "Optional normalized quality filter such as high, medium, low, or unknown.",
+  "maxLength": 64,
+  "minLength": 1,
+  "type": "string"
+}

changedOutput schema / description

Previous value: -"Ranked Phase 1 alpha-opportunity screen for the active DeltaSignal issuer universe."New value: +"DeltaSignal ATLAS-7 MCPResponse wrapper. Raw tool payload is returned under data."

addedOutput schema / properties / data / additionalProperties
```
Added value: +true
```

changedOutput schema / properties / data / description

Previous value: -"Ranked alpha-opportunity rows."New value: +"Ranked Phase 1 alpha-opportunity screen for the active DeltaSignal issuer universe. The default screen focuses on operating-company issuers and requires issuer drilldown; ETF/trust/fund/product vehicles require explicit opt-in."

removedOutput schema / properties / data / items

Removed value: -{
-  "additionalProperties": true,
-  "description": "Alpha opportunity row with ticker, score, risk, quality, debt coverage, treasury, and provenance fields.",
-  "type": "object"
-}

addedOutput schema / properties / data / properties

Added value: +{
+  "data": {
+    "description": "Ranked alpha-opportunity rows.",
+    "items": {
+      "additionalProperties": true,
+      "description": "Alpha opportunity row with ticker, CIK/entity metadata when available, issuer type, identity status, raw alpha score, board rank score, risk, quality, debt coverage, treasury, and provenance fields.",
+      "type": "object"
+    },
+    "type": "array"
+  },
+  "meta": {
+    "additionalProperties": true,
+    "description": "Pagination and count metadata.",
+    "properties": {
+      "count": {
+        "description": "Number of rows returned in data.",
+        "type": "integer"
+      },
+      "limit": {
+        "description": "Limit applied to the query.",
+        "type": "integer"
+      },
+      "offset": {
+        "description": "Offset applied to the query when available.",
+        "type": "integer"
+      },
+      "total": {
+        "description": "Total matching rows before pagination.",
+        "type": "integer"
+      }
+    },
+    "type": "object"
+  }
+}

addedOutput schema / properties / data / required
```
Added value: +[
+  "data",
+  "meta"
+]
```

changedOutput schema / properties / data / type

Previous value: -"array"New value: +"object"

addedOutput schema / properties / mcp_summary

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

removedOutput schema / properties / meta

Removed value: -{
-  "additionalProperties": true,
-  "description": "Pagination and count metadata.",
-  "properties": {
-    "count": {
-      "description": "Number of rows returned in data.",
-      "type": "integer"
-    },
-    "limit": {
-      "description": "Limit applied to the query.",
-      "type": "integer"
-    },
-    "offset": {
-      "description": "Offset applied to the query when available.",
-      "type": "integer"
-    },
-    "total": {
-      "description": "Total matching rows before pagination.",
-      "type": "integer"
-    }
-  },
-  "type": "object"
-}

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: -[
-  "data",
-  "meta"
-]New value: +[
+  "mcp_summary",
+  "data",
+  "provenance",
+  "suggested_follow_ups"
+]

AddedMay 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, and non-destructive; the description adds valuable behavioral disclosures: performs one HTTPS read, has no destructive side effects, and does not handle wallets, payments, orders, or account state. It also adds the interpretive caveat that high scores are drilldown candidates, not standalone conclusions.

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 dense but well-structured: a purpose sentence, a parameter summary, and a behavior section. It repeats some annotation terms (read-only, idempotent) and lists many fields, but every clause adds operational context, resulting in minimal waste for the information conveyed.

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?

Despite having an output schema, it provides a full operational picture: default behavior, parameter constraints (limit 1-100, source_date format), side effects, and an interpretation caveat. Combined with rich annotations and output schema, the description leaves no major ambiguity for an agent selecting or invoking this tool.

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 provides 100% parameter descriptions, so the baseline is 3. The description elevates this by explaining that source_date 'replays a known slice' and clarifying default behavior for issuer_type and include_funds, enriching the raw schema definitions.

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 opens with a specific verb and resource: 'screening tool to rank the active DeltaSignal issuer universe by deterministic Phase 1 alpha score.' It goes on to list concrete returned fields (ticker, CIK, alpha score, board rank, risk tier), which effectively differentiates it from sibling tools like alpha_signals and alpha_sweep.

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 usage context: default returns operating-company issuers, and include_funds=true or issuer_type=etf_trust|fund_vehicle|all should only be used when the user explicitly asks for ETF/trust/fund/product-vehicle screens. It lacks a direct comparison to named sibling tools, but the when-to-use guidance is explicit enough.

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?