Skip to main content
Glama

crypto-deep-analysis

Crypto deep analysis kit. The complete one-asset methodology: verified price and supply protocol, tokenomics and unlock schedule, on-chain holder forensics, protocol health, regulatory classification, derivatives positioning, red flags, and 3/5/7/10-year viability scenarios. One call returns the full kit; the buyer's agent runs the analysis itself. Research, not investment advice. Price: $10.00 per call, paid in USDC on Base mainnet over x402; an unpaid call answers HTTP 402 with the exact machine-readable payment terms.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "asset": "<asset>"
    },
    "name": "crypto-deep-analysis"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetYesThe crypto asset to analyze, e.g. BTC.
chainNoOptional chain hint (default base).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden, and it does disclose the most consequential trait: a $10.00 USDC-on-Base x402 payment requirement, plus the exact failure mode (HTTP 402 with machine-readable payment terms on an unpaid call). That is genuinely valuable context an agent cannot get from the schema. However, it says nothing about the returned payload's form or size — document versus structured data, latency, or whether the call is idempotent/repeatable — which matters for a paid tool.

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?

One dense paragraph, front-loaded with the identity and the deliverable inventory before the commercial terms. Every clause carries content, though the deliverable list is packed into a long comma run that could be split for scannability. No filler or marketing padding beyond 'complete'.

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?

There is no output schema and no annotations, so the description must define the return; enumerating kit components helps, but it never states the return format or granularity, which is a real gap for a paid call where the agent must decide before spending. Payment mechanics are fully covered, so the omission is confined to output shape and any per-asset coverage caveats.

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 coverage is 100%, so both 'asset' and 'chain' already carry their own descriptions with an example value and a default. The description adds only the framing that this is a one-asset methodology, which reinforces the cardinality of 'asset' but gives no format guidance, chain-hint effect, or behavior when the hint conflicts with the asset. Baseline 3 applies.

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

Purpose4/5

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

The description states a specific resource (a single crypto asset) and enumerates the concrete deliverables of the kit: verified price and supply, tokenomics and unlock schedule, holder forensics, protocol health, regulatory classification, derivatives positioning, red flags, and viability scenarios. It also clarifies the division of labor ('One call returns the full kit; the buyer's agent runs the analysis itself'), which distinguishes it from a tool that would return a finished verdict. It stops short of naming or contrasting with stock-deep-analysis, so sibling differentiation is left implicit.

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

Usage Guidelines3/5

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

Usage is implied rather than prescribed: it is for deep single-asset crypto research, and 'Research, not investment advice' sets a boundary on what the output means. There is no explicit statement of when to prefer this over a cheaper or narrower alternative, nor any when-not-to-use guidance, so an agent must infer fit from the deliverable list.

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