DeltaSignal ATLAS-7

DeltaSignal article TripCode resolve

deltasignal_resolve_article_tripcode

Read-onlyIdempotent

Use this read-only resolver tool to load a TF-SUB article/narrative research object from the TrendForge Azure Blob resolver lake. Parameters: tripcode is required and must be a proprietary DeltaSignal article resolver key such as TF-SUB-DA79A58372. Behavior: idempotent and read-only with no destructive side effects; it does not mutate Azure Blob, Substack, filings, wallets, or account state. Use this when a subscriber gives Codex or Claude Code a TripCode from an article subtitle and asks for the machine-readable research object behind the article.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tripcode`	Yes	Required TF-SUB article TripCode, for example TF-SUB-DA79A58372.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Resolved TF-SUB article/narrative research object from Azure Blob.
`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.

AddedJun 9, 2026
RemovedJun 8, 2026
AddedJun 8, 2026

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), the description adds specific context: 'idempotent and read-only with no destructive side effects; it does not mutate Azure Blob, Substack, filings, wallets, or account state.' This clarifies the exact scope of non-mutation, which is valuable for an agent.

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 tool's purpose, and each sentence serves a distinct function (purpose, parameters/behavior, usage scenario). No redundancy or extraneous content.

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 an output schema present, the description does not need to detail return values. The tool has only one parameter and is a simple resolver; the description fully covers its purpose, usage, and behavioral constraints, making it complete for an agent.

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 coverage is 100%, so baseline is 3. The description mentions the tripcode parameter and its required format, but this essentially restates the schema description. It adds no extra semantic detail beyond providing an example key.

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 it is a 'read-only resolver tool to load a TF-SUB article/narrative research object from the TrendForge Azure Blob resolver lake.' This indicates a specific verb (load/resolve), a specific resource (article/narrative research object), and differentiates from sibling tripcode resolvers for filings or rivers.

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?

The description provides a clear usage scenario: 'Use this when a subscriber gives Codex or Claude Code a TripCode from an article subtitle and asks for the machine-readable research object behind the article.' It lacks explicit when-not-to-use or alternative tool names, but the context is unambiguous.

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?