Skip to main content
Glama
Sign In
SicariusGuard

SicariusGuard

by Chronolapse411
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

check_nft

Analyze a Solana NFT’s safety by combining on-chain metadata with marketplace intelligence, returning a risk score and verdict.

Instructions

Perform a safety analysis on a Solana NFT combining Helius DAS on-chain metadata with Magic Eden marketplace intelligence. Returns riskScore (0-100), verdict (SAFE | CAUTION | HIGH_RISK | CRITICAL), collection verification status, floor price, volume, creator verification, and per-signal flags. Read-only — no on-chain side effects. Use this for NFTs; use check_token_safety for fungible SPL tokens.

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": "check_nft"
  }
}

Input Schema

NameRequiredDescriptionDefault
mintYesSolana NFT mint address (base58)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A5/5.0
Behavior5/5

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

States 'Read-only — no on-chain side effects,' which is critical behavioral info. Also describes data sources and return fields, compensating for missing annotations.

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?

Two sentences: first function and output, second usage guidance. No unnecessary words, heavily front-loaded.

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?

With one parameter, no output schema, but description enumerates return values (riskScore, verdict, etc.) and data sources, fully informing agent.

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

Parameters5/5

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

Schema has 100% coverage with description for 'mint' parameter. Description adds 'NFT' and 'base58,' providing extra semantic clarity beyond schema.

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 it performs a safety analysis on a Solana NFT, specifying data sources (Helius DAS, Magic Eden) and outputs. It also distinguishes from sibling tool check_token_safety for fungible tokens.

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

Usage Guidelines5/5

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

Explicitly says 'Use this for NFTs; use check_token_safety for fungible SPL tokens,' providing clear when-to-use and alternative.

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

Deploy Server

Other Tools