Skip to main content
Glama

ArcanumFleet Evolved Engrams

arcanum_engrams
Read-onlyIdempotent

Use this to retrieve the fleet's distilled order-flow, risk, and execution heuristics evolved from live trades and community signals. Costs 0.01 USDC via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "arcanum_engrams"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety and idempotency are covered. The description does add genuinely non-structured information — a 0.01 USDC x402 charge per call — which is exactly the kind of cost/auth context an agent needs before invoking. However, it says nothing about latency, caching, or whether the 0.01 USDC is per-call or per-session, leaving the payment model partially opaque.

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?

Two short sentences, with the purpose front-loaded and the cost constraint immediately after; there is no padding. Minor deductions for the filler opener 'Use this to' and for leaving the central noun 'engrams' unexplained while spending words on it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no parameters and no output schema, the description carries the full burden of telling an agent what comes back, and it only gestures at 'distilled heuristics' without describing shape, granularity, or freshness. For a paid, open-world retrieval tool this is a meaningful gap, though the cost disclosure and the annotations cover the invocation mechanics adequately.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly focuses on output content and cost rather than inventing parameter talk.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'retrieve' and the object 'order-flow, risk, and execution heuristics evolved from live trades and community signals' give a real sense of the content, but the flagship term 'engrams' is never defined, so the agent must guess what form the data takes. Nothing distinguishes it from conceptual neighbours like arcanum_smart_money or arcanum_social_sentiment, which also traffic in trade and community signals.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

'Use this to retrieve...' is an imperative but not actual guidance: there is no when-to-use condition, no when-not-to-use, and no named alternative among the eight siblings. An agent has no basis for choosing this over arcanum_pulse or arcanum_consensus_vote.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources