Skip to main content
Glama

DeltaSignal ATLAS-7

by net.aitrailblazer.api
OverviewAdmin

DeltaSignal SPECTRA field map

deltasignal_spectra_field_map
Read-onlyIdempotent

Use this read-only tool to retrieve the SPECTRA historical field-map contract for one crypto public company ticker. It returns issuer-specific filing choreography and pressure-map context used by DeltaSignal report and visualization workflows. Parameters: ticker is required and must be one public-company symbol such as RIOT, MARA, COIN, MSTR, HUT, or CLSK. Behavior: read-only and idempotent; it performs one HTTPS read, has no destructive side effects, and does not write files, wallets, orders, or account state. Use it when the user asks for SPECTRA, field-map, historical pressure, filing choreography, or report-visualization context for a named issuer.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tickerYesRequired crypto public company ticker symbol. Examples: RIOT, MARA, COIN, MSTR, HUT, CLSK.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesSPECTRA historical field-map contract for one issuer.
provenanceYesTraceability information for the MCP tool response.
mcp_summaryYesConcise high-signal summary of the tool response. Maximum 140 characters.
usage_metadataNoPerformance and estimated cost metadata for this MCP tool call.
suggested_follow_upsYesConcrete 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.

  1. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Required crypto public company ticker symbol or SEC CIK for no-ticker ATLAS-7 issuers. Examples: RIOT, MARA, COIN, MSTR, HUT, 0002081043."New value: +"Required crypto public company ticker symbol. Examples: RIOT, MARA, COIN, MSTR, HUT, CLSK."
  2. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Required crypto public company ticker symbol. Examples: RIOT, MARA, COIN, MSTR, HUT, CLSK."New value: +"Required crypto public company ticker symbol or SEC CIK for no-ticker ATLAS-7 issuers. Examples: RIOT, MARA, COIN, MSTR, HUT, 0002081043."
  3. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Required crypto public company ticker symbol or SEC CIK for no-ticker ATLAS-7 issuers. Examples: RIOT, MARA, COIN, MSTR, HUT, 0002081043."New value: +"Required crypto public company ticker symbol. Examples: RIOT, MARA, COIN, MSTR, HUT, CLSK."
  4. Changed1 schema field changed
    • changedInput schema / properties / ticker / description
      Previous value: -"Required crypto public company ticker symbol. Examples: RIOT, MARA, COIN, MSTR, HUT, CLSK."New value: +"Required crypto public company ticker symbol or SEC CIK for no-ticker ATLAS-7 issuers. Examples: RIOT, MARA, COIN, MSTR, HUT, 0002081043."
  5. Changed14 schema fields changed
    • changedInput schema / properties / ticker / maxLength
      Previous value: -16New value: +10
    • changedOutput schema / description
      Previous value: -"SPECTRA historical field-map contract for one issuer."New value: +"DeltaSignal ATLAS-7 MCPResponse wrapper. Raw tool payload is returned under data."
    • removedOutput schema / properties / contract
      Removed value: -{
-  "additionalProperties": true,
-  "description": "SPECTRA field-map contract payload, including historical pressure and filing-choreography fields when available.",
-  "type": "object"
-}
    • addedOutput schema / properties / data
      Added value: +{
+  "additionalProperties": true,
+  "description": "SPECTRA historical field-map contract for one issuer.",
+  "properties": {
+    "contract": {
+      "additionalProperties": true,
+      "description": "SPECTRA field-map contract payload, including historical pressure and filing-choreography fields when available.",
+      "type": "object"
+    },
+    "generated": {
+      "description": "Whether the response was generated dynamically rather than read from a stored contract.",
+      "type": "boolean"
+    },
+    "provenance": {
+      "additionalProperties": true,
+      "description": "Source/provenance metadata for the served contract.",
+      "type": "object"
+    },
+    "source": {
+      "description": "Source location or generation path for the field-map contract.",
+      "type": "string"
+    },
+    "status": {
+      "description": "Field-map contract status when available.",
+      "type": "string"
+    },
+    "ticker": {
+      "description": "Normalized public-company ticker symbol used for the field-map lookup.",
+      "type": "string"
+    }
+  },
+  "required": [],
+  "type": "object"
+}
    • removedOutput schema / properties / generated
      Removed value: -{
-  "description": "Whether the response was generated dynamically rather than read from a stored contract.",
-  "type": "boolean"
-}
    • addedOutput schema / properties / mcp_summary
      Added value: +{
+  "description": "Concise high-signal summary of the tool response. Maximum 140 characters.",
+  "type": "string"
+}
    • changedOutput schema / properties / provenance / description
      Previous value: -"Source/provenance metadata for the served contract."New value: +"Traceability information for the MCP tool response."
    • addedOutput schema / properties / provenance / properties
      Added value: +{
+  "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"
+  }
+}
    • removedOutput schema / properties / source
      Removed value: -{
-  "description": "Source location or generation path for the field-map contract.",
-  "type": "string"
-}
    • removedOutput schema / properties / status
      Removed value: -{
-  "description": "Field-map contract status when available.",
-  "type": "string"
-}
    • 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"
+}
    • removedOutput schema / properties / ticker
      Removed value: -{
-  "description": "Normalized public-company ticker symbol used for the field-map lookup.",
-  "type": "string"
-}
    • 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"
+]
  6. Added

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint=false), the description adds concrete behavioral detail: 'it performs one HTTPS read, has no destructive side effects, and does not write files, wallets, orders, or account state.' This explicitly enumerates non-side-effects and network behavior, going well beyond what annotations alone provide.

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 three sentences, front-loaded with the core purpose, then return value, parameter note, behavior, and usage. Every sentence earns its place 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?

The tool has one parameter, an output schema, and strong annotations. The description covers what it returns, when to use it, parameter requirements, and behavioral safety, making it fully complete for an agent to select and invoke correctly. The presence of an output schema removes the need to explain return fields.

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%, and the schema already fully documents the ticker parameter with pattern, min/max length, examples, and a description. The description's mention that ticker 'is required and must be one public-company symbol' adds no new semantic meaning beyond the schema, so the baseline score of 3 applies.

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: 'retrieve the SPECTRA historical field-map contract for one crypto public company ticker.' It further clarifies the output as 'issuer-specific filing choreography and pressure-map context,' distinguishing this tool from report, pressure-board, or quick-check siblings by the SPECTRA field-map contract focus.

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?

Explicit usage guidance is provided: 'Use it when the user asks for SPECTRA, field-map, historical pressure, filing choreography, or report-visualization context for a named issuer.' This gives clear trigger phrases and context, though it does not explicitly name alternative tools or state when not to use it, so it misses the 'when-not' exclusion for a 5.

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 toolsInspect
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