Skip to main content
Glama

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.

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).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered and the trailing 'Read-only' is largely redundant. The description does add value annotations can't, namely that results include metadata and marketplace operator approvals, but it says nothing about how unknown tokenIds or empty holdings behave.

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?

One front-loaded sentence covers both modes and the return payload, with zero filler. The final 'Read-only.' fragment is the only slightly wasteful element since annotations already state it.

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 3-parameter read-only lookup with no output schema, the description sets out both query modes and the kind of data returned, which is enough to invoke it correctly. Only error/empty-result behavior is left unstated, a minor gap given the rich annotations.

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, and the parenthetical mapping in the description simply restates it. Baseline 3 applies; no extra format or edge-case meaning is contributed.

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 names a specific resource (BlazarForce NFT) and disambiguates two distinct query modes: owner lookup by tokenId and holdings enumeration by address. It also states the extra payload (metadata, marketplace operator approvals). It stops short of naming a sibling it is not, so it doesn't reach 5.

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?

Usage is only implied through the parameter-parenthesis mapping: pass tokenId for ownership, owner for a token-id list. There is no explicit when-to-use/when-not guidance and no routing to blazar_nft_collections or blazar_nft_listings, which an agent could easily confuse with this tool.

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