Skip to main content
Glama

nft_catalogo

Read-onlyIdempotent

Catalogo das 65 pecas 0001sensations (extensao digital, Ethereum, Agosto 2021), agora arquivo historico gratuito -- ja nao licenciavel (ver licenca_formal). Com a ultima leitura conhecida do dono (owner_ultima_leitura + owner_verificado_em + owner_estado por item -- NAO e uma chamada on-chain ao vivo) e links directos OpenSea/Rarible. Para confirmacao on-chain agora mesmo de um token especifico, usa nft_owner_atual. (gratis)

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": "nft_catalogo"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  2. Changed2 schema fields changed
    • removedInput schema / properties / ref
      Removed value: -{
      -  "description": "Opcional. Codigo de referral de um parceiro/agente (o endereco Base dele). Nao afecta o pagamento — apenas atribui comissao contabilistica.",
      -  "type": "string"
      -}
    • removedInput schema / properties / tx_hash
      Removed value: -{
      -  "description": "Opcional. Hash da transaccao (0x...) apos pagar o preco em USDC na rede Base mainnet para a carteira sagrada. Omitir para receber as instrucoes de pagamento sem gastar nada.",
      -  "type": "string"
      -}
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Adds a crucial trait annotations cannot express: the owner fields (owner_ultima_leitura, owner_verificado_em, owner_estado) are a cached snapshot, explicitly NOT a live on-chain call. It also discloses the tool is free and read-only in effect, which goes beyond readOnlyHint/idempotentHint and prevents the agent from treating stale ownership data as authoritative.

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 identification (what the catalog is and its status) before the caveats and the alternative. The parentheticals and the trailing '(gratis)' are slightly redundant, but each clause carries real information; nothing essential is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no input parameters and no output schema, the description must describe what comes back, and it does: per-item owner state plus three timestamp/provenance fields and external marketplace links. Combined with the staleness warning and the sibling pointer, an agent has everything needed to call it and interpret the result correctly.

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 the baseline is 4 and the schema has nothing for the description to compensate for. The description instead spends its words on the returned owner fields, which is appropriate for a no-argument tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource (the 65-piece 0001sensations catalog on Ethereum, Aug 2021) and its current status as a free historical archive that is no longer licensable. It also names what the tool returns (last known owner snapshot plus OpenSea/Rarible links), so the agent can tell it apart from both licenca_formal and nft_owner_atual.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use nft_owner_atual for live on-chain confirmation of a specific token, and consult licenca_formal for licensing since this catalog is no longer licensable. Both the when-to-use and the when-not-to-use are stated, along with the sibling that covers the excluded case.

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.