Skip to main content
Glama

DeltaSignal ATLAS-7

by io.github.aitrailblazer

DeltaSignal ATLAS-7 CompanyFacts history

deltasignal_atlas7_companyfacts_history
Read-onlyIdempotent

Use this read-only tool to retrieve compact SEC CompanyFacts/XBRL materialization rows for the crypto public-company universe or a specific ticker/CIK. It returns one compact row per issuer for a materialized companyfacts source_date, including tag counts, crypto/digital-asset flags, top tags, taxonomies, evidence hashes, and fact source pointers. Parameters: source_date replays a known YYYY-MM-DD materialization slice; ticker or cik optionally narrows to one issuer; limit defaults to 25 and is capped at 250; offset paginates the universe. Behavior: read-only and idempotent; it performs no writes, has no destructive side effects, and never returns the raw facts_payload, so use fact_source_pointer plus evidence_hash for drilldown/audit. Use this for Mirror Pulse or ATLAS-7 historical joins when you need the compact issuer-level CompanyFacts inventory for all 215 crypto companies.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cikNoOptional SEC CIK. Accepts bare digits or CIK-prefixed form and normalizes to 10 digits.
modeNoOptional response mode. Use compact by default; summary includes the compact summary object.
limitNoMaximum issuer rows to return. Defaults to 25 and is capped at 250.
offsetNoPagination offset over compact issuer rows.
tickerNoOptional public-company ticker. Omit with cik to page the full materialized crypto issuer universe.
source_dateNoOptional materialized CompanyFacts source date in YYYY-MM-DD format. Defaults to the latest materialized source date.
include_summaryNoInclude the compact summary JSON object in each row.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesCompact materialized SEC CompanyFacts rows keyed by source_date and 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.

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds non-obvious behavior: it 'never returns the raw facts_payload' and directs users to use fact_source_pointer plus evidence_hash for drilldown/audit. This goes beyond the annotations and helps prevent misuse.

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 well-structured and front-loaded with the core purpose. Each sentence adds meaningful detail (return format, parameter behavior, safety guarantees, use cases) without fluff. It is appropriately sized for the tool's complexity.

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 description covers the return format (one compact row per issuer, listed fields), safety profile, parameter behavior, and intended use cases. With an output schema present and complete annotations, this description is fully 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 baseline is 3. The description adds behavioral meaning to parameters: source_date 'replays a known materialization slice', ticker/cik 'narrows to one issuer', limit 'defaults to 25 and is capped at 250', and offset 'paginates the universe.' These add value beyond the schema's field descriptions.

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 uses a specific verb ('retrieve') and identifies the exact resource ('compact SEC CompanyFacts/XBRL materialization rows') and scope (crypto public-company universe or a specific ticker/CIK). It clearly distinguishes itself from siblings like atlas7_calculation_history and deltasignal_atlas7_point_in_time_history by focusing on CompanyFacts materialization history.

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 when-to-use guidance: 'Use this for Mirror Pulse or ATLAS-7 historical joins when you need the compact issuer-level CompanyFacts inventory for all 215 crypto companies.' It names concrete use cases but does not explicitly mention alternatives or when not to use, so it falls short of 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.

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.

Resources