Skip to main content
Glama

DeltaSignal ATLAS-7

by io.github.aitrailblazer

DeltaSignal TripCode research packet

deltasignal_resolve_tripcode_research_packet
Read-onlyIdempotent

Use this read-only composite resolver as the default subscriber-facing TripCode tool. Parameters: tripcode is required and must be a public TF-SUB article TripCode. issuer, river_tripcode, limit, payload_mode, and include flags are optional. Behavior: read-only and idempotent with no destructive side effects; it resolves the current article object, discovers prior TF-SUB River nodes, runs the article thesis map, and returns one research_packet with article memory, River continuity, evidence refs, boundaries, missing evidence, and suggested follow-ups. It does not call Grok, does not mutate Azure Blob or Substack, does not invent missing evidence, and does not treat TripCodes as SEC identifiers or investment advice.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoOptional maximum prior article nodes to return. Defaults to 25.
issuerNoOptional issuer hint, such as HUT.
tickerNoOptional issuer hint alias.
tripcodeYesRequired TF-SUB article TripCode from a DeltaSignal article subtitle, for example TF-SUB-9DA70A7F98.
payload_modeNoOptional payload mode: compact or full. Compact is the default.
river_tripcodeNoOptional TF-RIVER root hint.
river_tripcodesNoOptional TF-RIVER root hints.
include_thesis_mapNoWhen true, include the thesis-map sections. The MVP defaults to running the thesis map.
include_unpublishedNoWhen true, include draft or unpublished article nodes when the caller is authorized.
include_article_bodyNoWhen true with available content, include article body fields. Compact mode returns metadata and hashes only.
include_prior_articlesNoWhen true, include discovered prior River nodes. The MVP defaults to including compact River nodes.
include_filing_evidenceNoWhen true, include filing evidence refs from the thesis map. The MVP keeps missing filing evidence explicit.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesOne TripCode-centered subscriber research packet across TF-SUB, TF-RIVER, TF-XBRL, and TF-DS continuity.
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.6/5.0
Behavior5/5

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

Annotations already provide readOnly, idempotent, and non-destructive hints. The description adds valuable context by naming specific non-behaviors (does not call Grok, does not mutate Azure Blob or Substack) and describing the internal resolution process (current article object, prior River nodes, thesis map). This exceeds the annotation baseline.

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?

The description is a single dense paragraph split into 'Parameters' and 'Behavior' segments. It is front-loaded with the purpose and every sentence adds value, but the length and density make it slightly harder to scan. Could be improved with bullet points, but 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?

For a composite tool with 12 parameters and an existing output schema, the description covers inputs, behavior, limitations, and output contents (article memory, River continuity, evidence refs, boundaries, missing evidence, suggested follow-ups). No significant gaps remain.

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 the baseline is 3. The description adds the 'public' constraint on tripcode and summarizes the optional parameter groups (issuer, river_tripcode, limit, payload_mode, include flags), which adds practical meaning beyond the schema 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 clearly states it is a read-only composite resolver and the default subscriber-facing TripCode tool. It specifies the resource (TripCode) and the action (resolves into a research packet), distinguishing it from sibling resolvers like deltasignal_resolve_article_tripcode.

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?

It explicitly positions itself as the default subscriber-facing TripCode tool, giving strong usage context. It also lists exclusions (does not call Grok, mutate storage, invent evidence, treat as SEC identifiers). However, it does not explicitly mention when to use alternative resolver tools, so it falls short of full guidance.

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