Skip to main content
Glama

DeltaSignal ATLAS-7

by net.aitrailblazer.api

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.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added
  2. Removed
  3. Added

TDQS

A4.5/5.0
Behavior5/5

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

The description adds valuable context beyond annotations: it is 'local for the MVP', 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. This goes beyond the idempotent/readOnly hints already provided.

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 economical: it opens with the purpose, then covers parameter requirements, behavioral attributes, and usage context in three sentences. No filler or redundancy.

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 output schema exists and annotations cover safety, the description sufficiently provides the purpose, behavior, and usage scenario. It even explains what is returned ('HUT seed objects') and a recommended workflow timing (before article comparison).

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 coverage is 100% and the description mostly repeats what the schema already says about 'tripcode' being required and format. It does add 'proprietary DeltaSignal SEC/XBRL resolver key' which provides a bit of extra meaning, but not substantial enough to exceed baseline.

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 specifies the exact action: load a TF-XBRL TripCode as a SEC/XBRL evidence object. It clearly distinguishes this from sibling tools by focusing on filing tripcodes (TF-XBRL) rather than article or 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?

The description gives a clear when-to-use context: 'Use this before article comparison whenever a Substack article names a TF-XBRL evidence object.' It does not explicitly name alternatives or state when-not-to-use, but the specificity to TF-XBRL implies the boundary.

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

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