CryptoBoss

get_meme_analyze

Rug risk analysis: risk score, flags, liquidity, holder analysis. $0.05.

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

Input Schema

Name	Required	Description	Default
`address`	Yes
`api_key`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedJul 11, 2026

TDQS

C2.3/5.0

Behavior2/5

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

No annotations exist; the description only adds a cost indicator ($0.05). It fails to disclose that an API key is required (only implied by the schema), whether the operation is read-only, or any rate limits. The behavioral burden is largely unmet.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely short (one sentence), which is efficient but omits critical details. It lacks structure and does not earn its place by being sufficiently informative. Truly concise descriptions pack essential information without waste; this under-serves the agent.

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

Completeness1/5

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

With no output schema, complex behavioral expectations (risk analysis output format), and limited annotations, the description is grossly incomplete. It fails to explain what the returned risk score or flags mean, or how to interpret liquidity and holder analysis results.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description provides no explanation of the 'address' or 'api_key' parameters. The agent cannot infer what address format to use or why the API key is needed. The description adds zero value over the raw schema.

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 clearly states the tool provides 'rug risk analysis' with specific outputs like risk score, flags, liquidity, and holder analysis. The name includes 'meme' and 'analyze', distinguishing it from siblings like 'get_meme_scan' (likely retrieval) and 'analyze_contract' (generic contract analysis).

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?

No guidance is given on when to use this tool versus alternatives. It mentions a cost ($0.05) but does not explain prerequisites, input requirements, or excluded use cases. The agent is left to infer from context among many siblings.

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

All CryptoBoss tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?