DeltaSignal ATLAS-7

DeltaSignal article-to-filing evidence compare

deltasignal_compare_article_to_filing_evidence

Read-onlyIdempotent

Use this read-only comparison tool to compare a TF-SUB article node against resolved TF-XBRL filing evidence objects. Parameters: article_tripcode is optional, filing_tripcodes may list one or more TF-XBRL objects, and ticker=HUT with no filing_tripcodes loads the default HUT filing pack. Behavior: idempotent and local for the MVP; it has no destructive side effects, does not mint official SEC identity, does not infer filing evidence from prose, and does not call wallets or x402 settlement. The HUT MVP returns a structured article-readiness packet with filing changes, confirmed thesis points, weakened assumptions, stress points, XBRL drivers, invalidation checks, and next-filing monitors.

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.
`article_tripcode`	No	Optional TF-SUB article node TripCode to compare against filing evidence.
`comparison_focus`	No	Optional comparison focus, such as HUT article readiness or thesis verification.
`filing_tripcodes`	No	Optional TF-XBRL filing evidence TripCodes. If omitted for HUT, the default HUT filing pack is used.
`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	Article-to-filing thesis verification packet backed by TF-XBRL resolver objects.
`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.7/5.0

Behavior5/5

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

Beyond the annotations, the description discloses idempotent and local MVP behavior, absence of destructive side effects, no SEC identity minting, no inference from prose, and no wallet/x402 calls. It also summarizes the returned packet structure, giving a complete behavioral picture.

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 well-organized sentences: purpose, parameters, and behavior. It is front-loaded with the core action and every sentence adds distinct value without filler or repetition.

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 18 parameters, an existing output schema, and rich annotations, the description covers the essential context: what the tool compares, how to invoke the default HUT scenario, key limits, and what the response contains. The schema fills in the remaining parameter details.

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?

The schema already describes all 18 parameters, so the baseline is 3. The description adds meaningful semantics for article_tripcode, filing_tripcodes, and the ticker=HUT default behavior, going beyond what the schema states without needing to repeat every field.

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: 'compare a TF-SUB article node against resolved TF-XBRL filing evidence objects.' It clearly identifies the input types and the read-only nature, which differentiates it from general-purpose comparison tools and aligns with the tool name.

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 invocation guidance: article_tripcode is optional, filing_tripcodes can list one or more TF-XBRL objects, and ticker=HUT with no filing_tripcodes loads the default pack. It lacks an explicit 'when not to use' or direct comparison against sibling tools, but the usage context is clear.

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.

Resources

Need Help?