Skip to main content
Glama

DeltaSignal ATLAS-7

by io.github.aitrailblazer

StrategiX visual-spec compact search

strategix_visual_spec_search
Read-onlyIdempotent

Search compact visual-spec metadata by topic, source digest, embedded contract hash, receipt hash, project, diagram family, and tags. Returns compact metadata only; full HTML/SVG/XML is a drilldown concern.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results. Defaults to 10.
queryYesSearch query across compact metadata and built-in MVP fixture records.
artifactsNoOptional caller-supplied compact metadata records to search.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is covered. The description adds the behavior that it returns only compact metadata and that full specs require a separate drilldown step, which is valuable context beyond the annotations.

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 two sentences with no fluff. The action verb leads, the searchable fields are enumerated compactly, and the return type caveat is stated clearly. 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?

With rich annotations, a detailed schema, and an output schema present, the description covers the essential purpose, searchable fields, and return type. The optional 'artifacts' parameter is documented in the schema, so its omission from the description does not create a gap.

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?

The schema descriptions are thorough (100% coverage), but the description adds meaning to the 'query' parameter by listing the specific searchable fields (topic, source digest, hash, etc.). This helps the agent understand what to put in the query, going beyond the generic schema text.

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 begins with 'Search compact visual-spec metadata' and lists specific search dimensions (topic, source digest, embedded contract hash, receipt hash, project, diagram family, tags), making the tool's function and scope immediately clear. It distinguishes from sibling tools like strategix_diagram_render or strategix_visual_spec_package by focusing on search and metadata.

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 states 'Returns compact metadata only; full HTML/SVG/XML is a drilldown concern,' which implicitly tells the agent to use this for metadata search and another tool for full specifications. While it doesn't name the alternative tool explicitly, the context is clear enough for correct tool selection.

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