DeltaSignal ATLAS-7

DeltaSignal SEC/XBRL TripCode generate

deltasignal_generate_filing_tripcode

Read-onlyIdempotent

Use this read-only SEC/XBRL identity tool to generate a deterministic TF-XBRL resolver object for a DeltaSignal evidence object. Parameters: pass ticker=HUT with no filing overrides for the HUT 2026-Q1 10-Q seed object, or provide cik, issuer, filing_type, filing_period, and source document fields for explicit generation. Behavior: idempotent and local for the MVP; it has no destructive side effects, does not modify SEC filings, does not call wallets or x402 settlement, and never replaces SEC accession numbers, CIKs, form types, reporting periods, or XBRL concept identities. Use the returned TripCode as a subscriber-facing join key from article nodes, research rivers, SEC evidence, and DeltaSignal outputs.

Input Schema

TableJSON Schema

Name	Required	Description
`cik`	No	SEC CIK, with or without CIK prefix.
`issuer`	No	Issuer ticker or short symbol. Prefer ticker for public companies.
`ticker`	No	Issuer ticker. HUT is the seeded MVP ticker.
`company`	No	SEC registrant company name.
`filing_date`	No	SEC filing date.
`filing_type`	No	SEC form type such as 10-Q or 8-K.
`report_date`	No	SEC report date or period end.
`filing_period`	No	Normalized filing period such as 2026-Q1.
`xbrl_instance`	No	XBRL instance document reference when available.
`primary_filing`	No	Primary SEC filing document reference.
`research_river`	No	Optional prior TF-SUB article TripCodes linked to this filing object.
`accession_number`	No	SEC accession number when the object is filing-specific.
`latest_article_node`	No	Optional latest TF-SUB article node linked to this filing evidence object.
`companyfacts_snapshot`	No	CompanyFacts snapshot reference when available.
`deltasignal_method_version`	No	Optional method version override for deterministic regeneration tests.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Generated SEC/XBRL TripCode 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.

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.6/5.0

Behavior5/5

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

Even with annotations declaring readOnlyHint, idempotentHint, and destructiveHint, the description adds significant detail: it is 'local for the MVP,' 'does not call wallets or x402 settlement,' and 'never replaces SEC accession numbers, CIKs, form types, reporting periods, or XBRL concept identities.' This goes well beyond the structured hints and clarifies the exact boundaries of side effects.

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 about 120 words across three sentences, front-loading the purpose and clearly labeling 'Parameters' and 'Behavior' sections. It is somewhat dense but every sentence contributes meaning, including safety constraints and downstream usage. It could be slightly more concise but remains well-structured.

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 has 15 parameters (all optional), a rich output schema, and many sibling tools, the description is comprehensive. It explains the two usage modes, the deterministic and side-effect-free behavior, and the practical downstream use as a subscriber-facing join key. No major gaps are apparent.

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?

With 100% schema description coverage, the baseline is 3, but the description adds value by explaining parameter combinations: the seed shortcut (ticker=HUT, no overrides) and the explicit path (cik, issuer, filing_type, filing_period, and source document fields). It does not fully detail each parameter but provides usage context beyond the schema.

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 the tool 'generate[s] a deterministic TF-XBRL resolver object for a DeltaSignal evidence object,' specifying the verb, resource, and output. It distinguishes this from sibling tools by emphasizing 'SEC/XBRL identity' and 'filing' tripcode generation, contrasting with article or river tripcode tools.

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 explicit usage context: use ticker=HUT with no overrides for the seed object, or provide explicit filing fields for generation. It also mentions downstream use as a join key. However, it does not explicitly name alternative tools (e.g., resolve_tripcode) or state when not to use this tool, so it falls short of full 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?