Skip to main content
Glama

DeltaSignal ATLAS-7

by io.github.aitrailblazer

DeltaSignal Coinbase perp rankings

deltasignal_coinbase_perp_rankings
Read-onlyIdempotent

Use this read-only tool to rank Coinbase INTX perp products by the latest persisted market_alpha row per product within the requested scope. It returns one latest factor row per product, ordered into a board with rank, percentile, ranking_score, ranking_band, and preserved factor provenance. Parameters: optional product or underlying_ticker filters, source_date or source_date_from/source_date_to, mode=compact|full, limit, and offset. Behavior: read-only and idempotent with no destructive side effects; it performs no live exchange fetches, order placement, or settlement flows.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
modeNoOptional response mode: compact or full.
limitNoMaximum ranked products to return. Defaults to 25 and is capped at 100 through MCP.
offsetNoPagination offset over ranked products.
productNoOptional Coinbase INTX product_id or contract_symbol filter.
source_dateNoOptional exact source date in YYYY-MM-DD format.
source_date_toNoOptional inclusive source-date upper bound in YYYY-MM-DD format.
source_date_fromNoOptional inclusive source-date lower bound in YYYY-MM-DD format.
underlying_tickerNoOptional underlying ticker filter.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesCoinbase INTX perp rankings built from the latest persisted factor row per product within scope.
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.7/5.0
Behavior5/5

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

Beyond the readOnly/idempotent hints, the description adds valuable contextual detail: it performs no live exchange fetches, order placement, or settlement flows. It also explains the return structure and idempotent nature, enriching the agent's understanding of side effects and operational characteristics.

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 three sentences with no redundancy. It front-loads the purpose, then summarizes outputs, parameters, and safety behavior. Every sentence earns its place, making it efficient and easy to parse.

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 rich annotations, output schema, and 100% parameter coverage, the description is fully self-sufficient. It covers purpose, output fields, parameter usage, and explicit non-behaviors, so an agent can invoke the tool correctly without additional investigation.

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?

While schema coverage is 100%, the description adds practical grouping ('product or underlying_ticker filters', 'source_date or source_date_from/source_date_to') and specifies mode=compact|full, which is not indicated as an enum in the schema. This helps agents understand parameter relationships and valid mode values.

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 the tool ranks Coinbase INTX perp products by the latest persisted market_alpha row per product, specifying the output board fields (rank, percentile, ranking_score, ranking_band, provenance). This gives a specific verb+resource+scope and distinguishes it from sibling tools like deltasignal_coinbase_perp_factors.

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 opens with 'Use this read-only tool to rank...', providing clear context and intended use. It doesn't explicitly name alternatives or exclusions, but the scope is well-defined and behavioral notes (no live fetches, no order placement) help agents decide. Lacks explicit 'when not to use' 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