Skip to main content
Glama
Sign In

Lorg Check

by com.lorglabs
OverviewDiscussionsAdmin

Check a token before buying it

check_token
Read-onlyIdempotent

Is this token safe to buy? Runs a simulated buy and sell-back through the token's real pool, and reads what its owner can still do, who can withdraw the pool's liquidity, its holders, its deployer and whether it imitates a known token. Returns a signed verdict (allow, caution or block), an action (proceed, limit_exposure, do_not_proceed), a one-sentence summary and the reasons, most serious first. Use it before every swap into a token on Base, Ethereum, Arbitrum, Robinhood Chain, Polygon or BNB Chain or Solana. Typically 1.3 seconds for a token checked from scratch; much faster for one checked moments earlier.

Input Schema

NameRequiredDescriptionDefault
chainYesThe chain the address is on.
addressYesThe token's contract address: 0x followed by 40 hex characters, or on Solana the token's mint address (base58, case matters).
amount_usdNoOptional: your trade's size in US dollars. The check then also buys and sells that amount in simulation, and says so (EXIT_LIQUIDITY_INSUFFICIENT) when the pool or the token can't take it. Give it whenever you know the size.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"The token's contract address: 0x followed by 40 hex characters."New value: +"The token's contract address: 0x followed by 40 hex characters, or on Solana the token's mint address (base58, case matters)."
    • changedInput schema / properties / address / pattern
      Previous value: -"^0x[0-9a-fA-F]{40}$"New value: +"^(0x[0-9a-fA-F]{40}|[1-9A-HJ-NP-Za-km-z]{32,44})$"
    • changedInput schema / properties / amount_usd / description
      Previous value: -"Optional: the size of the trade you intend, in US dollars. The check then also buys and sells that amount in simulation, and says so (EXIT_LIQUIDITY_INSUFFICIENT, action limit_exposure) when the pool is too small for it or the token limits the size of a sale. Give it whenever you know the size."New value: +"Optional: your trade's size in US dollars. The check then also buys and sells that amount in simulation, and says so (EXIT_LIQUIDITY_INSUFFICIENT) when the pool or the token can't take it. Give it whenever you know the size."
    • changedInput schema / properties / chain / enum
      Previous value: -[
-  "base",
-  "ethereum"
-]New value: +[
+  "base",
+  "ethereum",
+  "arbitrum",
+  "robinhood",
+  "polygon",
+  "bnb",
+  "solana"
+]
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false; the description adds real substance on top: the check is a simulation against the live pool (not an actual buy), it discloses what sources it inspects, it explains the returned verdict/action structure, and it gives expected latency (~1.3s cold, faster when cached). Nothing contradicts the readOnly annotation because the trade is explicitly described as simulated.

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?

It opens with the decision the agent cares about ("Is this token safe to buy?"), then gives the mechanism, the return shape, the usage trigger and the performance profile in that order. Every sentence carries distinct information; nothing is padded.

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

Completeness5/5

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

There is no output schema, so the description has to describe return values, and it does: signed verdict (allow/caution/block), an action (proceed/limit_exposure/do_not_proceed), a one-sentence summary and reasons ordered by severity. With annotations covering the safety profile and the schema covering all three parameters, nothing an agent needs is missing.

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%, so chain, address and amount_usd are already fully documented in the schema, including base58/hex formats and the amount_usd bounds. The description adds only indirect meaning by enumerating the supported chains in prose, which mostly restates the chain enum, so baseline 3 is right.

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 states a specific verb and resource (simulated buy/sell-back through the token's real pool, plus owner/liquidity/holder/deployer/imitation checks) and frames it as a safety verdict. An agent can immediately tell this is a token risk check rather than an address lookup, which is what the sibling check_address implies.

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?

"Use it before every swap into a token on Base, Ethereum, Arbitrum, Robinhood Chain, Polygon or BNB Chain or Solana" gives clear, concrete context for when to call it, and the latency note tells the agent that repeat calls are cheap. It does not name the sibling check_address or state when not to use this tool, so no alternatives or exclusions are covered.

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

All Lorg Check toolsInspect
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