DeltaSignal ATLAS-7

DeltaSignal help

deltasignal_help

Read-onlyIdempotent

Use this free read-only discovery-tier tool when the user asks for help, available commands, MCP tools, core concepts, pricing, parser-stable fields, grants, x402, Morning Brief, Company Report, MSTR treasury review, perp adapters, SPECTRA, or examples. Parameters: optional topic, detail, include_examples, question, or query fields; callers may omit all arguments for overview help. Behavior: local and idempotent with no destructive side effects; it does not run paid analysis routes or expose internal-only tools. It translates natural-language orientation requests into the live DeltaSignal MCP/OpenAPI discovery contract and points users to tools/list, /v1/pricing, /v1/contract/fields, and /v1/readiness. It is not a trading, execution, or investment-advice tool and must not expose internal-only tools unless the live public contract lists them.

Input Schema

TableJSON Schema

Name	Required	Description
`query`	No	Alias for question for clients that pass a generic query field.
`topic`	No	Optional help topic.
`detail`	No	Optional detail level. short returns a compact guide; full includes more examples and boundary notes.
`question`	No	Optional natural-language help question, such as 'what can I ask Delta Signal?' or 'help pricing'.
`include_examples`	No	Include example MCP tool-call payloads and safe next commands. Defaults to true when omitted.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Free DeltaSignal MCP discovery and orientation 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.

Changed5 schema fields changedJul 1, 2026

changedInput schema / properties / topic / enum

Previous value: -[
-  "overview",
-  "concepts",
-  "tools",
-  "integration",
-  "pricing",
-  "fields",
-  "parser_contract",
-  "grants",
-  "x402",
-  "morning_brief",
-  "company_report",
-  "mstr",
-  "perps",
-  "spectra",
-  "examples"
-]New value: +[
+  "overview",
+  "groups",
+  "concepts",
+  "tools",
+  "integration",
+  "pricing",
+  "fields",
+  "parser_contract",
+  "grants",
+  "x402",
+  "morning_brief",
+  "company_report",
+  "mstr",
+  "crypto_lanes",
+  "synthetic_ai10",
+  "perps",
+  "spectra",
+  "examples"
+]

addedOutput schema / properties / data / properties / crypto_native_lanes

Added value: +{
+  "description": "Public crypto-native lane map with example normalized issuers.",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / help_groups

Added value: +{
+  "description": "Human-readable DeltaSignal help groups and their specific help commands.",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / issuer_coverage

Added value: +{
+  "additionalProperties": true,
+  "description": "Public summary of issuer and synthetic-lane coverage counts.",
+  "type": "object"
+}

addedOutput schema / properties / data / properties / synthetic_lane_coverage

Added value: +{
+  "description": "Public synthetic-lane coverage summary.",
+  "items": {
+    "additionalProperties": true,
+    "type": "object"
+  },
+  "type": "array"
+}

Changed4 schema fields changedJun 29, 2026

addedOutput schema / properties / data / properties / developer_schema_preview

Added value: +{
+  "additionalProperties": true,
+  "description": "Compact developer-facing paths for rendering and integration; production parser fields still come from /v1/contract/fields.",
+  "type": "object"
+}

addedOutput schema / properties / data / properties / provenance_defaults

Added value: +{
+  "description": "Explains why local help responses may not carry source-dated market or issuer provenance.",
+  "type": "string"
+}

addedOutput schema / properties / data / properties / recommended_discovery_path

Added value: +{
+  "description": "Ordered onboarding steps for safe MCP and REST discovery before execution.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

addedOutput schema / properties / data / properties / terminology

Added value: +{
+  "additionalProperties": true,
+  "description": "Compact distinction between Synthetic AI10, perps, and SPECTRA.",
+  "type": "object"
+}

AddedJun 29, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already provide readOnlyHint=true, idempotentHint=true, destructiveHint=false, and the description adds concrete behavioral context: 'local and idempotent with no destructive side effects; it does not run paid analysis routes or expose internal-only tools.' This explains what the tool avoids, which is beyond the structured annotations. No contradictions.

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?

Three sentences, each earning its place: trigger conditions, parameter summary + behavior, and boundary/exclusion note. Uses 'Parameters:' and 'Behavior:' labels for internal structure. No fluff or repetition, front-loaded with the most important guidance.

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 is a help/discovery helper with an output schema present, the description covers purpose, parameters, behavior, exclusions, and alternative resources. It even explains it translates natural-language queries into the live DeltaSignal discovery contract, which is rich context for an agent. Nothing essential is missing.

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?

Schema description coverage is 100%, with every parameter already described (topic enum, detail enum, question alias, etc.). The description merely lists the parameter names and says they are optional, adding no semantics beyond the schema. Baseline 3 is appropriate because the schema fully carries parameter meaning.

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: 'Use this free read-only discovery-tier tool when the user asks for help' and enumerates exactly which topics are covered (pricing, fields, grants, etc.). It clearly distinguishes itself from sibling data tools by positioning itself as the help/orientation tool, not a data-returning tool.

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?

It states explicit trigger conditions ('when the user asks for help, available commands, MCP tools, core concepts...') and also gives exclusions: 'not a trading, execution, or investment-advice tool.' It points users to specific alternatives like tools/list and /v1/pricing, and mentions that omitting all arguments gives overview help. This is exemplary when-to-use guidance.

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?