DeltaSignal ATLAS-7

DeltaSignal Coinbase perp calculation history

deltasignal_coinbase_perp_calculation_history

Read-onlyIdempotent

Use this read-only tool to retrieve Coinbase INTX perp market-factor history assembled from persisted recorder evidence. It returns venue-pure calculation-history rows with contract identity, ATLAS-shaped factor fields, deltas, quality state, and optional full market inputs or lineage. 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 does not fetch live exchange data on demand, place trades, or mutate recorder state.

Input Schema

TableJSON Schema

Name	Required	Description
`mode`	No	Optional response mode: compact or full.
`limit`	No	Maximum calculation-history rows to return. Defaults to 25 and is capped at 100 through MCP.
`offset`	No	Pagination offset over calculation-history rows.
`product`	No	Optional Coinbase INTX product_id or contract_symbol filter, for example AI-PERP-INTX.
`source_date`	No	Optional exact source date in YYYY-MM-DD format.
`source_date_to`	No	Optional inclusive source-date upper bound in YYYY-MM-DD format.
`source_date_from`	No	Optional inclusive source-date lower bound in YYYY-MM-DD format.
`underlying_ticker`	No	Optional underlying ticker filter, for example AI or COIN50.

Output Schema

TableJSON Schema

Name	Required	Description
`data`	Yes	Coinbase INTX perp market-factor history assembled from persisted venue-pure recorder evidence.
`provenance`	Yes	Traceability information for the MCP tool response.
`mcp_summary`	Yes	Concise high-signal summary of the tool response. Maximum 140 characters.
`usage_metadata`	No	Performance and estimated cost metadata for this MCP tool call.
`suggested_follow_ups`	Yes	Concrete 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.

AddedJun 23, 2026
RemovedJun 23, 2026
AddedJun 21, 2026

TDQS

A4.3/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 by specifying the data source (persisted recorder evidence), the output's venue-pure nature, and explicit exclusions (no live exchange data, no trading, no recorder mutation). This goes beyond the annotations but does not mention error conditions or rate limits.

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 fluff: it front-loads the purpose, summarizes return content, lists parameters, and clarifies behavior. Every sentence earns its place.

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 is complete. It explains the tool's scope, output composition, parameter options, and non-behaviors, making it sufficient for an agent to select and invoke correctly.

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%, and the description merely lists parameter names and modes without adding deeper meaning. The schema already documents each parameter well, including examples, so the description adds little beyond restating them.

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 retrieves Coinbase INTX perp market-factor history from persisted recorder evidence, with a specific listing of returned fields (contract identity, ATLAS-shaped factors, deltas, quality state). This distinguishes it from siblings like deltasignal_coinbase_perp_factors or deltasignal_coinbase_perp_rankings by emphasizing calculation-history rows.

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 clear context for use: a read-only historical retrieval tool that does not fetch live data or place trades. However, it does not explicitly name alternative tools or provide when-not-to-use conditions, so it falls short of a 5.

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 tools Inspect

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.

Resources

Need Help?