Skip to main content
Glama

DeltaSignal ATLAS-7

by io.github.aitrailblazer

DeltaSignal SEC/XBRL TripCode resolve

deltasignal_resolve_filing_tripcode
Read-onlyIdempotent

Use this read-only resolver tool to load a TF-XBRL TripCode as a SEC/XBRL evidence object. Parameters: tripcode is required and must be a proprietary DeltaSignal SEC/XBRL resolver key such as TF-XBRL-HUT-2026Q1-... Behavior: idempotent and local for the MVP; it has no destructive side effects, does not mutate SEC filings, does not call wallets or x402 settlement, and returns HUT seed objects when the TripCode is known. Use this before article comparison whenever a Substack article names a TF-XBRL evidence object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tripcodeYesRequired SEC/XBRL TripCode, for example TF-XBRL-HUT-2026Q1-A8F31C2D9B.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesResolved SEC/XBRL TripCode object.
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.3/5.0
Behavior5/5

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

Annotations already mark readOnly/idempotent; description adds 'does not mutate SEC filings, does not call wallets or x402 settlement' and 'returns HUT seed objects when known,' going beyond annotation metadata.

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?

Four sentences that front-load purpose, then params, behavior, and usage. There is minor redundancy with annotations (e.g., 'no destructive side effects'), but the structure is clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Description covers purpose, parameter, behavior, and usage context. Output schema exists, so return values don't need explanation; unknown-tripcode behavior is not specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 100% coverage with type, required, min/max length, and example. Description repeats the requirement and adds 'proprietary DeltaSignal resolver key,' but most parameter semantics are already in 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?

Description states 'load a TF-XBRL TripCode as a SEC/XBRL evidence object' with a specific verb and resource. The tool name and context distinguish it from sibling resolve tools for article/river tripcodes.

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?

States 'Use this before article comparison whenever a Substack article names a TF-XBRL evidence object.' This gives a clear use case but doesn't explicitly exclude alternatives like resolve_article_tripcode.

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