boo-mpp-mcp

Token snapshot (price + supply + safety)

token_snapshot

Combine token price, supply, and safety checks into a single call, reducing API costs by avoiding three separate requests.

Instructions

One-shot token overview: price, supply and safety flags combined. Cheaper than three separate calls.

PAID TOOL: up to $0.015 USDC.e per call (MPP on Tempo). Paid automatically from your configured wallet.

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": {
      "token": "<token>",
      "chain": "<chain>"
    },
    "name": "token_snapshot"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	Yes	Chain: eth, bnb, base, solana.
`token`	Yes	Token contract address.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.1Aug 6, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations provided, the description conveys the key behavioral trait of being a paid tool (up to $0.015 USDC.e per call, paid automatically). It also implies a read-only 'snapshot' nature. However, it does not disclose details like what happens on insufficient balance or data freshness, which would warrant a higher score.

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

Conciseness5/5

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

The description is compact, with two sentences: the first states purpose and cost advantage, the second explains payment details. Every sentence adds value and the most important information is front-loaded.

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

Completeness4/5

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

Although there is no output schema, the description provides a high-level summary of what is returned (price, supply, safety flags). It also covers cost and payment, which is critical context. It doesn't elaborate on 'safety flags' or MPP specifics, but for a simple snapshot tool this is reasonably complete.

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?

The input schema has 100% description coverage, fully defining both parameters (token contract address and chain). The description adds no additional parameter-level semantics, so the baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the tool is a 'one-shot token overview' combining price, supply, and safety flags, which distinctly sets it apart from sibling tools like token_price, token_supply, and token_rugcheck. It also emphasizes the cost advantage, reinforcing its purpose.

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

Usage Guidelines4/5

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

The description explicitly says it's 'cheaper than three separate calls', implying when to use this tool instead of calling the individual price, supply, and safety tools. However, it does not explicitly state when NOT to use it (e.g., if only one data point is needed), but the context is clear.

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