Skip to main content
Glama
Sign In

presign-guard

by io.github.Fizzl13
OverviewDiscussionsAdmin

Token verdict ($0.01 via x402)

token_verdict
Read-only

Paid ($0.01 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand or Stellar, in RLUSD on the XRP Ledger or in USD₮0 on X Layer): call this before your agent buys, holds or accepts a token. Send the chain (solana, base, ethereum, arbitrum, optimism, polygon, bsc, robinhood, avalanche, xlayer, xrpl, algorand) and the token address, mint, CURRENCY.rIssuer or Algorand asset id; get back green/orange/red, a grade (SAFE, CAUTION, RISKY, AVOID), reason codes (mint or freeze authority still active, honeypot, tax or transfer fee, LP not locked, low liquidity, new token, concentrated holders, rugged), a one-line summary, and market data (price, liquidity, market cap, 24h volume, age). Same as GET /v1/token. The answer carries a signed receipt (EIP-191, bound to your arguments) that proves later which verdict you got.

Input Schema

NameRequiredDescriptionDefault
chainYesChain the token lives on
addressYesSolana mint address (base58), EVM token contract (0x...), XRPL token as CURRENCY.rIssuer, or Algorand asset id (e.g. 31566704)

Output Schema

NameRequiredDescriptionDefault
gradeNo
acceptsNoOnly on an unpaid call: the x402 payment options
reasonsNo
receiptNo
verdictNogreen: go ahead; orange: ask the user; red: do not sign or buy (absent on the payment requirement)
versionNo
one_linerNoOne-line summary

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
-  "solana",
-  "base",
-  "ethereum",
-  "arbitrum",
-  "optimism",
-  "polygon",
-  "bsc",
-  "robinhood",
-  "avalanche",
-  "xlayer",
-  "xrpl",
-  "algorand"
-]New value: +[
+  "solana",
+  "base",
+  "ethereum",
+  "arbitrum",
+  "optimism",
+  "polygon",
+  "bsc",
+  "robinhood",
+  "avalanche",
+  "xlayer",
+  "monad",
+  "xrpl",
+  "algorand"
+]
  2. Changed10 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedOutput schema / additionalProperties
      Previous value: -trueNew value: +{}
    • changedOutput schema / properties / accepts / anyOf
      Previous value: -[
-  {
-    "items": {
-      "additionalProperties": {},
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "items": {
+      "additionalProperties": {},
+      "propertyNames": {
+        "type": "string"
+      },
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • addedOutput schema / properties / grade / anyOf
      Added value: +[
+  {
+    "description": "SAFE, CAUTION, RISKY or AVOID",
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / grade / description
      Removed value: -"SAFE, CAUTION, RISKY or AVOID"
    • removedOutput schema / properties / grade / type
      Removed value: -[
-  "string",
-  "null"
-]
    • changedOutput schema / properties / reasons / anyOf
      Previous value: -[
-  {
-    "description": "Why the verdict is what it is",
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "code": {
-          "description": "Reason code, e.g. SPENDER_FLAGGED, UNLIMITED_ALLOWANCE, TOKEN_HONEYPOT",
-          "type": "string"
-        },
-        "severity": {
-          "description": "info, warn or critical",
-          "type": "string"
-        },
-        "subject": {
-          "description": "The address or item the reason is about (null or absent when it is about the whole request)",
-          "type": [
-            "string",
-            "null"
-          ]
-        }
-      },
-      "required": [
-        "code"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Why the verdict is what it is",
+    "items": {
+      "additionalProperties": {},
+      "properties": {
+        "code": {
+          "description": "Reason code, e.g. SPENDER_FLAGGED, UNLIMITED_ALLOWANCE, TOKEN_HONEYPOT",
+          "type": "string"
+        },
+        "severity": {
+          "description": "info, warn or critical",
+          "type": "string"
+        },
+        "subject": {
+          "description": "The address or item the reason is about (null or absent when it is about the whole request)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "code"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / reasons / description
      Removed value: -"Why the verdict is what it is"
    • changedOutput schema / properties / receipt / anyOf
      Previous value: -[
-  {
-    "additionalProperties": {},
-    "description": "Signed receipt (EIP-191) binding the verdict to your arguments",
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "additionalProperties": {},
+    "description": "Signed receipt (EIP-191) binding the verdict to your arguments",
+    "propertyNames": {
+      "type": "string"
+    },
+    "type": "object"
+  },
+  {
+    "type": "null"
+  }
+]
    • removedOutput schema / properties / receipt / description
      Removed value: -"Signed receipt (EIP-191) binding the verdict to your arguments"
  3. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
-  "solana",
-  "base",
-  "ethereum",
-  "arbitrum",
-  "optimism",
-  "polygon",
-  "bsc",
-  "robinhood",
-  "avalanche",
-  "xrpl",
-  "algorand"
-]New value: +[
+  "solana",
+  "base",
+  "ethereum",
+  "arbitrum",
+  "optimism",
+  "polygon",
+  "bsc",
+  "robinhood",
+  "avalanche",
+  "xlayer",
+  "xrpl",
+  "algorand"
+]
  4. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
-  "solana",
-  "base",
-  "ethereum",
-  "arbitrum",
-  "optimism",
-  "polygon",
-  "bsc",
-  "robinhood",
-  "xrpl",
-  "algorand"
-]New value: +[
+  "solana",
+  "base",
+  "ethereum",
+  "arbitrum",
+  "optimism",
+  "polygon",
+  "bsc",
+  "robinhood",
+  "avalanche",
+  "xrpl",
+  "algorand"
+]
  5. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
-  "solana",
-  "base",
-  "ethereum",
-  "arbitrum",
-  "optimism",
-  "polygon",
-  "bsc",
-  "xrpl",
-  "algorand"
-]New value: +[
+  "solana",
+  "base",
+  "ethereum",
+  "arbitrum",
+  "optimism",
+  "polygon",
+  "bsc",
+  "robinhood",
+  "xrpl",
+  "algorand"
+]
  6. Changed1 schema field changed
    • changedOutput schema / properties / reasons / anyOf
      Previous value: -[
-  {
-    "description": "Why the verdict is what it is",
-    "items": {
-      "additionalProperties": true,
-      "properties": {
-        "code": {
-          "description": "Reason code, e.g. SPENDER_FLAGGED, UNLIMITED_ALLOWANCE, TOKEN_HONEYPOT",
-          "type": "string"
-        },
-        "severity": {
-          "description": "info, warn or critical",
-          "type": "string"
-        },
-        "subject": {
-          "description": "The address or item the reason is about",
-          "type": "string"
-        }
-      },
-      "required": [
-        "code"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "description": "Why the verdict is what it is",
+    "items": {
+      "additionalProperties": true,
+      "properties": {
+        "code": {
+          "description": "Reason code, e.g. SPENDER_FLAGGED, UNLIMITED_ALLOWANCE, TOKEN_HONEYPOT",
+          "type": "string"
+        },
+        "severity": {
+          "description": "info, warn or critical",
+          "type": "string"
+        },
+        "subject": {
+          "description": "The address or item the reason is about (null or absent when it is about the whole request)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "required": [
+        "code"
+      ],
+      "type": "object"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]
  7. Changed2 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"Solana mint address (base58) or EVM token contract (0x...)"New value: +"Solana mint address (base58), EVM token contract (0x...), XRPL token as CURRENCY.rIssuer, or Algorand asset id (e.g. 31566704)"
    • changedInput schema / properties / chain / enum
      Previous value: -[
-  "solana",
-  "base",
-  "ethereum",
-  "arbitrum",
-  "optimism",
-  "polygon",
-  "bsc",
-  "xrpl"
-]New value: +[
+  "solana",
+  "base",
+  "ethereum",
+  "arbitrum",
+  "optimism",
+  "polygon",
+  "bsc",
+  "xrpl",
+  "algorand"
+]
  8. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "accepts": {
+      "anyOf": [
+        {
+          "items": {
+            "additionalProperties": {},
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Only on an unpaid call: the x402 payment options"
+    },
+    "grade": {
+      "description": "SAFE, CAUTION, RISKY or AVOID",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "one_liner": {
+      "description": "One-line summary",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "reasons": {
+      "anyOf": [
+        {
+          "description": "Why the verdict is what it is",
+          "items": {
+            "additionalProperties": true,
+            "properties": {
+              "code": {
+                "description": "Reason code, e.g. SPENDER_FLAGGED, UNLIMITED_ALLOWANCE, TOKEN_HONEYPOT",
+                "type": "string"
+              },
+              "severity": {
+                "description": "info, warn or critical",
+                "type": "string"
+              },
+              "subject": {
+                "description": "The address or item the reason is about",
+                "type": "string"
+              }
+            },
+            "required": [
+              "code"
+            ],
+            "type": "object"
+          },
+          "type": "array"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Why the verdict is what it is"
+    },
+    "receipt": {
+      "anyOf": [
+        {
+          "additionalProperties": {},
+          "description": "Signed receipt (EIP-191) binding the verdict to your arguments",
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "Signed receipt (EIP-191) binding the verdict to your arguments"
+    },
+    "verdict": {
+      "anyOf": [
+        {
+          "description": "green: go ahead; orange: ask the user; red: do not sign or buy",
+          "enum": [
+            "green",
+            "orange",
+            "red"
+          ],
+          "type": "string"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "green: go ahead; orange: ask the user; red: do not sign or buy (absent on the payment requirement)"
+    },
+    "version": {
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}
  9. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
-  "solana",
-  "base",
-  "ethereum",
-  "arbitrum",
-  "optimism",
-  "polygon",
-  "bsc"
-]New value: +[
+  "solana",
+  "base",
+  "ethereum",
+  "arbitrum",
+  "optimism",
+  "polygon",
+  "bsc",
+  "xrpl"
+]
  10. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds genuinely new behavior: it is a paid call ($0.01) with itemized accepted payment rails and currencies, and the response carries an EIP-191 signed receipt bound to the caller's arguments. It does not mention payment failure modes (what happens on an unpaid or underpaid request) or rate limits, which keeps it short of a 5.

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?

Everything is packed into one long sentence, and the lead clause is the payment-rail enumeration rather than the tool's purpose, which buries the front-loaded value. The nine-chain x402 payment list is verbose relative to its decision value.

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 paid read-only lookup with a full input schema and an output schema, the description covers cost, payment method, inputs and the shape of the verdict, which is more than enough to invoke it correctly. The main omission is the relationship to token_quick_verdict and any auth/payment-error behavior.

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% and both parameters are already documented in the schema, including the per-chain address formats (base58 mint, 0x contract, CURRENCY.rIssuer, Algorand asset id). The description restates the same formats and chain names rather than adding constraints, so the baseline 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?

Names a specific deliverable (a green/orange/red verdict plus grade, reason codes and market data) and the exact resource (a token on a named chain), so the agent knows precisely what it gets. It does not differentiate itself from the sibling token_quick_verdict, which is the obvious near-duplicate an agent would need to choose between.

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?

"Call this before your agent buys, holds or accepts a token" gives an explicit trigger condition. There are no when-not conditions and no mention of token_quick_verdict as the cheaper/faster alternative, so the routing between siblings is left to inference.

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

All presign-guard 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