Skip to main content
Glama

Blazar Polygon plugin

NFT listing info

blazar_nft_listings
Read-onlyIdempotent

Listing info for a BlazarForce NFT: owner, the site-stated ask, on-chain marketplace approvals (OpenSea Seaport conduit), and live Rarible orders only if RARIBLE_API_KEY is set in your env. There is no on-chain BlazarForce marketplace. Polygon only (chain 137).

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": {
      "collection": "<collection>"
    },
    "name": "blazar_nft_listings"
  }
}

Input Schema

NameRequiredDescriptionDefault
tokenIdNoDefault 1.
collectionYesCollection symbol, id or address: SLPV (Sleepy Validators), STUB (Night Market Stubs), MOTH (Crystal Moths).

Output Schema

NameRequiredDescriptionDefault
noteNo
linksNo
ownerNo
addressNo
raribleNo
tokenIdNo
collectionNo
onchainSignalsNo
siteStatedAskPolNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly/idempotent/non-destructive), the description discloses that results are assembled from several off-chain/on-chain sources, that Rarible data is conditional on an env key, and that no on-chain BlazarForce marketplace exists. It does not cover failure modes (unknown collection, missing approvals) but adds substantial context annotations cannot express.

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

Conciseness4/5

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

Three tight sentences that lead with what the caller gets, then behavioral caveats, then the chain constraint. No filler; the marketplace disclaimer earns its place by preventing a wrong assumption about on-chain listing state.

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 two-parameter read tool with full schema coverage, annotations, and an output schema, this is close to complete: chain scope, data sources, and conditional availability are all stated. Only the behavior on unknown collections or absent approvals is left unaddressed.

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%, with the collection parameter already listing sample symbols and tokenId carrying a default and bounds. The description adds no parameter-level meaning beyond that, 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?

States a specific verb+resource: listing info for a BlazarForce NFT, enumerating what is returned (owner, site-stated ask, marketplace approvals, Rarible orders). It implicitly differentiates from build/transfer siblings by being a read-only info tool, but never names an alternative like blazar_nft_holder, so differentiation is partial.

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?

Useful constraints are given: Polygon only (chain 137) and Rarible orders only when RARIBLE_API_KEY is set. However, there is no explicit when-to-use-vs-sibling guidance (e.g., versus blazar_nft_holder or blazar_nft_collections), so the agent must infer the routing itself.

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