Skip to main content
Glama

Blazar Polygon plugin

BlazarForce NFT collections

blazar_nft_collections
Read-onlyIdempotent

BlazarForce NFT collections on Polygon (Sleepy Validators, Night Market Stubs, Crystal Moths): live name, supply, holder count, top holders, interfaces, sample token URI, site-stated ask, marketplace links. Read-only. Polygon only (chain 137).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "blazar_nft_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
collectionsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so 'Read-only' in the description adds no new information. The genuinely additive piece is the hard scope limit 'Polygon only (chain 137)', which constrains the otherwise open-world hint and tells the agent not to expect other chains. Nothing is said about data freshness, caching, or whether the collection set is fixed versus dynamically discovered.

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?

Front-loaded with the resource and chain in the opening phrase, then the field list, then the two constraints. The long field enumeration partially duplicates the output schema and could be trimmed, but it is compact and contains no filler sentences.

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?

Output schema exists, so the return shape need not be spelled out, and with zero parameters there is nothing else structural to cover. The description supplies the chain restriction and the collection names, which is what an agent needs to decide to call it. Minor gaps: it does not say whether the three named collections are the full set or examples, nor how current the ask/marketplace data is.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly does not fabricate parameter guidance, since the input schema is an empty object.

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?

Names the specific resource (BlazarForce NFT collections on Polygon) and enumerates the exact fields returned: name, supply, holder count, top holders, interfaces, sample token URI, site-stated ask, marketplace links. This is far more specific than a tautology and lets an agent distinguish it from write-oriented siblings like blazar_build_nft_transfer. It stops short of explicitly contrasting with the closest read siblings (blazar_nft_holder, blazar_nft_listings, blazar_contracts).

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 description implies usage by describing the payload (collection metadata lookup) and the constraint 'Polygon only (chain 137)', which effectively excludes other chains. However, it gives no explicit when-to-use statement and never names an alternative tool for per-holder or listing-level queries, so the agent must infer routing from sibling names alone.

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