Skip to main content
Glama

sol_lp_check

Read-onlyIdempotent

How much liquidity is locked/burned — rug-pull setup detector — What share of the liquidity pool is locked or burned for any SPL mint (via RugCheck): strong / partial / weak, with the locked percentage. Weak LP = the deployer can pull liquidity (classic rug). If RugCheck does not report LP, you are not charged. Not advice. Required input: mint. Priced $0.02 per call over x402 on Base; send a prepaid x-credit-token header for unlimited calls, or get 1 free call/day per tool. No API key required.

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": {
      "mint": "<mint>"
    },
    "name": "sol_lp_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana SPL mint address

Output Schema

NameRequiredDescriptionDefault
dataNoThe result payload. Shape is service-specific; every field is documented in the tool description.
serviceNoThe service id that answered.
checkedAtNoISO-8601 timestamp of when the underlying reads were taken.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the annotations (readOnly, openWorld, idempotent, non-destructive), the description discloses the upstream data source (RugCheck), the no-charge condition when LP is unreported, pricing ($0.02/call over x402 on Base), the prepaid x-credit-token header path, and the free-call allowance. The only substantive gap is that it does not describe behavior on invalid or non-SPL mints, which the safety annotations already partly cover.

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

Conciseness3/5

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

The core purpose and the strong/partial/weak semantics are front-loaded, but the text is a dense dash-separated run-on that mixes purpose, interpretation, failure policy, and payment mechanics without clear separation. Nothing is truly wasted, yet readability suffers from the packaging.

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?

For a one-parameter read tool with a full output schema and complete annotations, the definition covers what an agent needs: the source, the rating semantics, the failure/no-charge behavior, and how payment works. It stops short of explaining edge cases such as mints with no pool at all, but the essentials are present.

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 description coverage is 100% and there is a single required parameter already documented as 'Solana SPL mint address'. The description only restates 'Required input: mint', adding no format, chain constraint, or example beyond the schema, so the baseline of 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 measurement (share of LP locked or burned for an SPL mint) and the verdict it produces (strong / partial / weak plus a locked percentage), which is far more concrete than a name restatement. It does not, however, distinguish itself from clearly adjacent siblings such as lp_lock or sol_liquidity, so an agent must infer which of those to pick.

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 context is implied rather than stated: 'rug-pull setup detector' and 'Weak LP = the deployer can pull liquidity (classic rug)' tell the agent the scenario this fits, but there is no explicit when-to-use/when-not-to-use language and no named alternative for overlapping liquidity checks.

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