Skip to main content
Glama

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.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so 'Read-only' is redundant. The valuable addition is the enumeration of returned data fields, which partly compensates for the missing output schema. It still omits freshness/caching behavior, whether the three named collections are the complete fixed set, and how 'site-stated ask' should be interpreted (untrusted/self-reported).

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?

A single front-loaded sentence delivers the resource, chain, and field inventory, followed by a short qualifier. The parenthetical collection names consume space without aiding tool selection, but overall there is little waste.

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 zero-parameter, no-output-schema reader, the description supplies the essential missing piece: what fields come back. Combined with annotations covering safety, an agent has enough to call it correctly. Remaining gaps (data freshness, whether the collection set is exhaustive) are minor rather than blocking.

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?

With zero parameters and 100% schema coverage, there is nothing for the description to disambiguate. The baseline for a no-parameter tool applies; the listing of returned fields is a bonus rather than required parameter documentation.

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 collections on Polygon) and enumerates exactly what the tool surfaces: name, supply, holder count, top holders, interfaces, sample token URI, ask, marketplace links. An agent can tell this is a collection-level metadata/catalog reader. It does not, however, distinguish itself from siblings like blazar_nft_holder or blazar_nft_listings, so sibling differentiation is left to the reader.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use, when-not-to-use, or alternative-tool guidance. 'Read-only' declares a property, not a condition for selection. An agent cannot tell from the text whether to call this versus blazar_nft_holder for holder data or blazar_nft_listings for marketplace data, even though overlap is obvious.

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