DeltaSignal ATLAS-7

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

Name	Required	Description
`cik`	No	Optional SEC CIK. Accepts bare digits or CIK-prefixed form and normalizes to 10 digits.
`mode`	No	Optional response mode. Use compact by default; summary includes the compact summary object.
`limit`	No	Maximum issuer rows to return. Defaults to 25 and is capped at 250.
`offset`	No	Pagination offset over compact issuer rows.
`ticker`	No	Optional public-company ticker. Omit with cik to page the full materialized crypto issuer universe.
`source_date`	No	Optional materialized CompanyFacts source date in YYYY-MM-DD format. Defaults to the latest materialized source date.
`include_summary`	No	Include the compact summary JSON object in each row.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Compact materialized SEC CompanyFacts rows keyed by source_date and issuer.
`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.

AddedMay 14, 2026

TDQS

A4.9/5.0

Behavior5/5

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

Annotations already declare read-only, idempotent, and non-destructive hints; the description reinforces these and adds key behavioral context: it never returns the raw facts_payload and directs users to fact_source_pointer/evidence_hash for deeper inspection. No contradiction with 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 four dense sentences with no filler, front-loading the purpose, then parameters, behavior, and use case. Each sentence earns its place given the tool's 7 optional parameters.

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 doesn't need to detail return values. It covers the purpose, usage context, parameter behavior, and key constraints (no raw payload, universe size of 215), making it complete for a read-only retrieval tool.

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 valuable semantic context beyond schema by explaining source_date as replaying a materialization slice, ticker/cik narrowing to one issuer, limit capping at 250, and offset paginating. It does not mention mode or include_summary, but those are self-explanatory in 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?

Clearly states it retrieves compact SEC CompanyFacts/XBRL materialization rows for the crypto public-company universe, with a specific verb (retrieve) and resource. It distinguishes itself from sibling tools by specifying the issuer-level inventory and materialization slice concept.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use this tool ('for Mirror Pulse or ATLAS-7 historical joins') and what to use instead for drilldown/audit (fact_source_pointer plus evidence_hash), providing clear alternatives and exclusions.

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?