Skip to main content
Glama

Blazar Polygon plugin

NFT owner / holdings

blazar_nft_holder
Read-onlyIdempotent

Who owns a BlazarForce NFT (tokenId), or which token ids an address holds (owner), with metadata and marketplace operator approvals. Read-only. 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_holder"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerNoList the token ids this address holds.
tokenIdNoLook up one token's owner and metadata.
collectionYesCollection symbol, id or address: SLPV (Sleepy Validators), STUB (Night Market Stubs), MOTH (Crystal Moths).

Output Schema

NameRequiredDescriptionDefault
linksNo
ownerNo
addressNo
balanceNo
tokenIdNo
metadataNo
tokenIdsNo
tokenURINo
collectionNo
metadataNoteNo
approvedOperatorNo
operatorApprovalsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so 'Read-only' is largely redundant. The description still adds genuine context beyond them: the hard chain restriction (Polygon only, chain 137) and the fact that results include metadata and marketplace operator approvals, which tells the agent what it will actually receive.

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?

A single sentence front-loads the dual purpose, then appends the read-only and chain constraints. Every clause carries information and nothing is padded.

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?

With an output schema present and annotations covering the safety profile, the description need not explain return values, and it correctly fills in the chain scope and the approvals-in-output detail. The one gap is behavior when only the required 'collection' is supplied with neither tokenId nor owner — the description doesn't say what that returns.

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 each parameter is already documented in the schema, including the allowed collection symbols and address pattern. The description reinforces the tokenId/owner semantics but adds no format, default, or interaction details beyond the schema; 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?

The description states a specific verb+resource and clearly spells out the two lookup modes: owner-by-tokenId and tokenIds-by-owner, both scoped to BlazarForce NFTs. It is not tautological and an agent can immediately tell this is a read lookup rather than a transfer/approval builder like the blazar_build_nft_* siblings, though it never names an alternative explicitly.

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?

The parenthetical parameter mapping ('tokenId' vs 'owner') implicitly tells the agent which mode to pick, which is useful routing guidance. However, there is no explicit when-to-use/when-not guidance and no pointer to sibling tools such as blazar_nft_listings or blazar_nft_collections, so the choice is left to inference from the parameter names.

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