Skip to main content
Glama

DeltaSignal ATLAS-7

by io.github.aitrailblazer

DeltaSignal River reverse search

deltasignal_reverse_search_river
Read-onlyIdempotent

Use this read-only thesis-lineage tool to start from a TripCode, issuer, claim, filing, or current object and reconstruct what the River already covered. Parameters: pass river_tripcode, issuer, seed_tripcode, query, claim_text, claim_hash, mode, include_xbrl, or include_ds. Output preserves the subscriber eight-section thesis-map shape: changed across River, confirmed signals, weakened assumptions, bridge risks, milestones, scenarios, invalidation, and next monitors. Behavior: deterministic graph synthesis with no destructive side effects, not an LLM or trading layer. Missing evidence remains missing.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoReverse-search mode: resolve, thesis_delta, claim_lineage, evidence_backtrace, invalidation_search, confirmation_search, monitoring_search, or scenario_rebuild.
limitNoOptional maximum result rows. Defaults to 25.
queryNoOptional reverse-search question or claim.
riverNoOptional TF-RIVER TripCode or issuer shorthand.
issuerNoOptional issuer ticker.
tickerNoOptional ticker alias for issuer.
tripcodeNoOptional TF-RIVER TripCode or TF-SUB seed TripCode.
claim_hashNoOptional normalized claim hash for by_claim_hash lookup.
claim_textNoOptional claim text to compare against the River.
include_dsNoWhen true, include TF-DS computed signal refs from the River object.
time_windowNoOptional time window label for caller-side filtering.
include_xbrlNoWhen true, include TF-XBRL evidence refs from the River object.
seed_tripcodeNoOptional seed TF-SUB, TF-XBRL, TF-DS, or TF-RIVER TripCode.
river_tripcodeNoOptional TF-RIVER TripCode.
river_tripcodesNoOptional known TF-RIVER TripCodes.
article_tripcodeNoOptional current TF-SUB article TripCode alias.
current_tripcodeNoOptional current TF-SUB article TripCode.
include_unpublishedNoWhen true, include draft or unpublished article nodes.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesReverse search across one issuer River.
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.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive. The description adds valuable context with 'deterministic graph synthesis' and 'Missing evidence remains missing,' which go beyond the annotations and clarify expected behavior.

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 concise and front-loaded with purpose. It uses three sentences to cover purpose, parameters, output shape, and behavior, with no redundant fluff.

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?

For a complex tool with 18 parameters and an output schema, the description adequately covers purpose, inputs, output shape, and behavior. The output schema fills in return-value details, making the description sufficient.

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 description coverage is 100%, so the schema already documents all 18 parameters. The description merely lists the parameter names without adding new semantics, leaving the baseline at 3.

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 a specific verb ('reconstruct') and resource ('what the River already covered'), and identifies multiple input seed types (TripCode, issuer, claim, filing). The reverse-search purpose distinguishes it from sibling tools like search_by_claim and article_thesis_map.

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 explicitly says when to use the tool ('start from... and reconstruct what the River already covered') and provides an exclusion ('not an LLM or trading layer'). It does not name alternative tools but gives clear context and parameter hints.

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