DeltaSignal ATLAS-7

DeltaSignal article TripCode generate

deltasignal_generate_article_tripcode

Read-onlyIdempotent

Use this read-only identity tool to generate a deterministic TF-SUB resolver object for a DeltaSignal-owned article or narrative research node. Parameters: primary issuer/ticker, title, research_slug, research_date, and optional research_version define the stable DeltaSignal identity. Substack post_id, canonical_url, slug, and published_at are publication metadata only and must not change the TripCode. Behavior: idempotent and local with no destructive side effects; it does not write Azure Blob, does not mutate Substack, and does not call wallets or x402 settlement. Use the returned TripCode in the article subtitle and the returned canonical blob paths in the authoring/sync pipeline.

Input Schema

TableJSON Schema

Name	Required	Description
`title`	Yes	Article title. Required for the article payload, but not hashed when research_slug is supplied.
`author`	No	Article author or publication author.
`issuer`	No	Primary issuer symbol when ticker is not supplied.
`ticker`	No	Primary issuer ticker. Alias for issuer/primary_issuer.
`post_id`	No	Optional Substack post ID. Secondary publication metadata only.
`platform`	No	Publication platform. Defaults to Substack.
`subtitle`	No	Article subtitle before TripCode writeback.
`publication`	No	Publication name. Defaults to DeltaSignal.
`research_id`	No	Optional explicit DeltaSignal research ID. If omitted, issuer + research_slug + research_date + version form the canonical identity.
`thesis_line`	No	Optional concise thesis line. Defaults to title.
`article_body`	No	Optional article body used only for content hash/provenance, not canonical TripCode identity.
`published_at`	No	Optional publication timestamp. Secondary publication metadata only.
`canonical_url`	No	Optional public canonical URL. Secondary publication metadata only.
`claim_summary`	No	Optional claim summary bullets.
`research_date`	Yes	Stable DeltaSignal research date in YYYY-MM-DD form.
`research_slug`	Yes	Stable DeltaSignal research slug, for example hut-8-re-rating-deadline.
`river_tripcodes`	No	Optional linked TF-RIVER TripCodes.
`research_version`	No	Optional research version. Defaults to 1.
`publication_state`	No	Optional article state such as draft or published_or_linked.
`linked_ds_tripcodes`	No	Optional linked TF-DS signal TripCodes.
`monitoring_checklist`	No	Optional monitoring checklist.
`linked_xbrl_tripcodes`	No	Optional linked TF-XBRL evidence TripCodes.
`invalidation_checklist`	No	Optional invalidation checklist.
`prior_article_tripcodes`	No	Optional prior TF-SUB TripCodes in this River.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Generated TF-SUB article/narrative research resolver object.
`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.

TDQS

A4.7/5.0

Behavior5/5

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

Even with annotations (readOnlyHint, idempotentHint, destructiveHint) present, the description adds valuable behavioral detail: deterministic, local, no Azure Blob writes, no Substack mutation, no wallet/x402 calls, and the guarantee that publication metadata does not affect the TripCode. This goes well beyond the annotations.

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 compact, front-loaded with the tool's purpose, and each sentence carries useful information: identity formation, metadata exclusions, safety behavior, and application. No filler 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?

Given the 24-parameter schema and an output schema, the description does not need to enumerate every field or return value. It highlights required identity fields, explicitly excludes non-identity metadata, and describes side-effect-free behavior. This is sufficient for an agent to select and invoke the tool correctly.

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?

Schema coverage is 100%, so the baseline is 3. The description adds meaningful grouping: identity-defining parameters (issuer/ticker, title, research_slug, research_date, research_version) versus publication metadata (post_id, canonical_url, published_at), helping the agent distinguish essential from non-essential inputs. The reference to 'slug' is slightly inconsistent with schema parameter names but does not undermine the overall semantic value.

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 states a specific verb and resource: 'generate a deterministic TF-SUB resolver object for a DeltaSignal-owned article or narrative research node.' It clearly distinguishes this from sibling tools like deltasignal_generate_filing_tripcode by focusing on article/narrative nodes, and from resolve/list tools by emphasizing generation.

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 gives clear context: 'Use this read-only identity tool to generate...' and explains the output's use in 'the article subtitle and the returned canonical blob paths in the authoring/sync pipeline.' It does not explicitly name alternative tools or exclusion criteria, but the context strongly implies when it is appropriate.

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

C2.8/5.0

Disambiguation2/5

The tool set has extensive overlap: natural-language variants duplicate raw JSON tools (e.g., deltasignal_covenant_stress vs deltasignal_covenant_stress_natural), composite workflow tools duplicate low-level screens (deltasignal_alpha_sweep vs deltasignal_alpha_opportunities), and the atlas7_* and deltasignal_* prefixes repeat the same concepts (e.g., atlas7_covenant_stress vs deltasignal_covenant_stress). An agent would likely struggle to pick the right tool for a given intent.

Naming Consistency2/5

Three distinct prefixes (atlas7_, deltasignal_, strategix_) are used, and duplicate tool names appear across prefixes (e.g., atlas7_readiness vs deltasignal_readiness). Verb patterns are inconsistent, mixing nouns and verbs (atlas7_archive_search, deltasignal_thesis_create, deltasignal_morning_brief_natural), and there is no clear rule for raw, natural, composite, or resolver variants.

Tool Count1/5

With 81 tools, the server is massively over-scoped. Many are near-duplicates or overlapping composites; the core domain likely needs 20-30 tools at most. The count is far beyond what an agent can reasonably navigate, and it indicates a failure to consolidate or version the surface.

Completeness3/5

The set covers a broad range of functionality: screening, stress, alpha, peer comparison, history, tripcode resolution, synthetic ETF state, and thesis monitoring. However, there are lifecycle gaps (e.g., thesis_create has no corresponding update/delete, and the atlas7 vs deltasignal split leaves no unified surface). The duplication suggests comprehensive coverage in some areas and awkward holes in others.

DeltaSignal article TripCode generate

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources