Check if an NFT is flagged as an airdrop by providing its contract address and token ID across multiple networks.
Check if a specific NFT is flagged as an airdrop
| Name | Required | Description | Default |
|---|---|---|---|
| network | No | Network ID. Call listSupportedNetworks for all options. e.g. "eth-mainnet", "base-mainnet" | eth-mainnet |
| contractAddress | Yes | Contract address of the NFT. | |
| tokenId | Yes | The token ID to check. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose any behavioral traits, such as whether the check is read-only, performance characteristics, or error conditions.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single sentence concisely conveys the purpose with no superfluous information; front-loaded structure.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Lacks details on return value or output format, and no behavioral context is provided despite the absence of annotations and output schema.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
All three parameters are described in the input schema with clear descriptions, so the description adds no additional meaning beyond what is already provided.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
Description clearly states the action ('check') and the resource ('specific NFT flagged as airdrop'), distinguishing it from other NFT tools like getNFTMetadata or getNFTSales.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this tool versus alternatives or any context for its appropriate use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/alchemyplatform/alchemy-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server