Skip to main content
Glama
@caelaralabs/mcp

@caelaralabs/mcp

caelara_crypto_token_safety_composite

Evaluate EVM or Solana token safety before trading by checking contract and mint authority, holder concentration, liquidity depth, pool age, and trade-flow flags.

Instructions

[On-Chain Intelligence] Safety score for an EVM or Solana token: contract/mint authority checks, holder concentration, on-chain liquidity depth, pool age and trade-flow flags Measured p50 12 ms, p95 14 ms (2026-11-21, benchmarks.caelaralabs.com). Calls https://crypto.caelaralabs.com.

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": {
      "address": "<address>"
    },
    "name": "caelara_crypto_token_safety_composite"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoChain: base|ethereum|arbitrum|optimism (default base)
addressYesToken contract (0x...) or Solana mint address

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.4/5.0
Behavior4/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 does meaningful work: it discloses exactly which checks produce the score, so the agent knows this is a composite read over contract authority, holder distribution, liquidity, age, and flow rather than a price or balance lookup. It also publishes measured p50/p95 latency and the backing endpoint, which is real operational context. Gaps remain around auth/credit cost, rate limits, and failure behavior for an invalid or unindexed address.

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?

The core purpose and the signal list are front-loaded immediately after the bracketed category tag, and the whole thing is three sentences long. The latency benchmark and endpoint URL are mildly promotional but still operationally relevant; the '[On-Chain Intelligence]' prefix is the only pure decoration.

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?

No output schema exists, so the description should explain what a 'safety score' actually returns — scale, whether flags are listed individually, or how a partial/inconclusive result appears. It describes inputs and score composition well but says nothing about the response shape, and its Solana claim is unsupported by the chain enum, leaving a material gap for a composite call.

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 parameters are already documented with chain options and the 'default base' note; the description only adds that the address may be an EVM contract or a Solana mint. That addition is genuinely useful for interpreting `address`, but it conflicts with the `chain` enum (base|ethereum|arbitrum|optimism), which has no Solana value, leaving the agent unsure how to request a Solana token. That unresolved mismatch caps this at baseline.

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 verb and resource ('Safety score for an EVM or Solana token') and enumerates the exact signals rolled into the score: authority checks, holder concentration, liquidity depth, pool age, trade-flow flags. This lets an agent distinguish it from narrow siblings such as dex_liquidity_depth or solana_mint_auditor, but it never names those siblings, so differentiation has to be inferred from the component list.

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?

There is no when-to-use or when-not-to-use guidance, no prerequisite or alternative routing, and no statement of what to do if the narrower single-signal tools would suffice. The only implied usage is a pre-trade token safety check, which an agent must derive itself; the latency and endpoint lines add no routing guidance.

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

Deploy Server

Other Tools