Skip to main content
Glama

nft_owner_atual

Read-onlyIdempotent

Le o dono real de UM token 0001sensations directamente da Ethereum mainnet (ownerOf), agora mesmo -- nao uma cache. Devolve owner_atual, rpc_usado, bloco consultado e verificado_em. So aceita um token_id por pedido (nunca lista os 65 de uma vez -- isso e nft_catalogo). ownerOf prova o dono naquele bloco; NAO prova que a peca esta listada para venda no OpenSea/Rarible -- esses links continuam sendo so consulta. (gratis)

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": {
      "token_id": "<token_id>"
    },
    "name": "nft_owner_atual"
  }
}

Input Schema

NameRequiredDescriptionDefault
token_idYesNumero do token a confirmar agora mesmo on-chain (ver nft_catalogo para a lista de token_ids validos).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / token_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / token_id / minimum
      Added value: +1
    • changedInput schema / properties / token_id / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / required
      Added value: +[
      +  "token_id"
      +]
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds genuinely new behavior: the read is live on-chain ("agora mesmo -- nao uma cache"), it is block-scoped, and it enumerates the returned fields (owner_atual, rpc_usado, bloco consultado, verificado_em). It also discloses a key limitation the annotations cannot express -- ownership does not imply OpenSea/Rarible listing.

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-loads the core action and the on-chain/no-cache qualifier before the sibling routing and the listing caveat. Slightly dense with parenthetical asides, but each clause carries distinct, useful information.

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?

No output schema exists, yet the description names all four returned fields, the data source, and the freshness guarantee. For a single-parameter read tool, nothing an agent needs to call it correctly or interpret the result is missing.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents token_id, its range, and points to nft_catalogo. The description reinforces the single-token constraint but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 verb and resource ("Le o dono real de UM token ... directamente da Ethereum mainnet (ownerOf)") and immediately names the sibling it is not ("nunca lista os 65 de uma vez -- isso e nft_catalogo"). An agent can distinguish it from nft_catalogo without opening either schema.

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?

Gives explicit usage context: one token_id per request, use nft_catalogo for the full list, and a clear scope exclusion (ownerOf does not prove marketplace listing). The alternatives and boundaries are named rather than implied.

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.