Skip to main content
Glama

Caelara Labs On-Chain Intelligence

token_safety_composite

Safety score for an EVM or Solana token: contract/mint authority checks, holder concentration, DEX liquidity depth, pool age and trade-flow flags

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": "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 observed

TDQS

B3.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It implies a read-only scoring lookup and discloses the analytical dimensions, but says nothing about latency, rate limits, caching, what happens on unsupported chains, or whether the score is a number, a letter grade, or a verdict with flags.

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, front-loaded clause with no filler; the resource and output come first and the component list follows. It is a noun phrase rather than a sentence, so it reads slightly like a label, but nothing is wasted.

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 output schema, the description must explain what comes back. It lists the dimensions checked but not the shape or scale of the score, how flags are surfaced, or what a low result means. It is adequate to decide to call the tool but thin for interpreting the response or resolving the Solana chain question.

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 the baseline is 3, and the description adds only the EVM/Solana scope. It actually introduces an ambiguity: the description and the address param both reference Solana mints, yet the chain enum lists only base|ethereum|arbitrum|optimism, so the agent cannot tell how Solana is selected. That gap is not resolved in the description.

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 names a specific resource (an EVM or Solana token) and a specific output (a composite safety score), then enumerates the components that feed it: authority checks, holder concentration, liquidity depth, pool age, trade-flow flags. This is clearly distinguishable from a price tool or a checksum validator, though it never names the overlapping siblings (dex_liquidity_depth, solana_mint_auditor) that could produce a similar answer for one dimension.

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 explicit when-to-use or when-not-to-use guidance. An agent can infer this is for pre-trade due diligence, but nothing states whether to prefer this composite over the narrower dex_liquidity_depth or solana_mint_auditor siblings, or whether it should be run on every token or only when a full audit is warranted.

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