Skip to main content
Glama

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.

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

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?

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: Rarible orders appear only if RARIBLE_API_KEY is set in the environment, and the ask price is site-stated rather than enforced on-chain. That conditional-output and trust caveat is exactly the kind of 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?

It is a single dense sentence covering return contents, the env-gated Rarible path, and the no-on-chain-marketplace caveat, with the primary payload front-loaded. It is efficient, though the middle clause about Seaport conduit is slightly jargon-heavy without payoff for an agent.

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-only lookup with no output schema, the definition covers what is returned, the one environmental prerequisite, and a key limitation of the data's authority. Missing only edge-case behavior such as what is returned when a token is unlisted, which is a minor gap given the tool's simplicity.

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 coverage is 100%, so both parameters (collection with example symbols, tokenId with a default) are already fully documented. The description adds no syntax, format, or scoping detail about the parameters themselves, 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?

The description names the resource (a BlazarForce NFT's listing data) and enumerates exactly what is returned: owner, site-stated ask, on-chain Seaport approvals, and live Rarible orders. That is far more specific than a tautology. It stops short of 5 because it never names a sibling (e.g. blazar_nft_holder) to contrast against, so the agent must infer the boundary itself.

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 implied rather than stated: this is the tool to call when you need to know who owns a token and what it is asking. The line 'There is no on-chain BlazarForce marketplace' is a useful negative signal that curbs wasted lookups, but there is no explicit 'use X instead when...' guidance and no preconditions for calling it.

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