Skip to main content
Glama

nft_dedicar

Publica uma dedicatoria apos o servico comparar wallet declarado com ownerOf na Ethereum. Nao pede assinatura, nao autentica controlo da carteira nem autorizacao do remetente. ownerOf nao e prova de autoria do pedido. Escreve registo publico; conservacao permanente nao garantida. Requer token_id, wallet, nome. (gratis; controlo da carteira nao autenticado)

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>",
      "wallet": "<wallet>",
      "nome": "<nome>"
    },
    "name": "nft_dedicar"
  }
}

Input Schema

NameRequiredDescriptionDefault
nomeYesComo queres ser lembrado.
walletYesA tua carteira Ethereum que possui o NFT agora.
mensagemNoOpcional.
token_idYesNumero do token NFT que compraste (ver nft_catalogo).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • addedInput schema / properties / mensagem / maxLength
      Added value: +400
    • addedInput schema / properties / nome / maxLength
      Added value: +80
    • addedInput schema / properties / nome / minLength
      Added value: +1
    • addedInput schema / properties / nome / pattern
      Added value: +"\\S"
    • 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 / properties / wallet / maxLength
      Added value: +42
    • addedInput schema / properties / wallet / minLength
      Added value: +42
    • addedInput schema / properties / wallet / pattern
      Added value: +"^0x[0-9a-fA-F]{40}$"
    • addedInput schema / required
      Added value: +[
      +  "token_id",
      +  "wallet",
      +  "nome"
      +]
  2. Changed4 schema fields changed
    • changedInput schema / properties / mensagem / description
      Previous value: -"Opcional. Uma mensagem poetica ou dedicatoria, max 400 caracteres."New value: +"Opcional."
    • changedInput schema / properties / nome / description
      Previous value: -"Como queres ser lembrado, ligado à obra para sempre. Max 80 caracteres."New value: +"Como queres ser lembrado."
    • changedInput schema / properties / token_id / description
      Previous value: -"O numero do token NFT (1 a 65+) que compraste, ver nft_catalogo."New value: +"Numero do token NFT que compraste (ver nft_catalogo)."
    • changedInput schema / properties / wallet / description
      Previous value: -"A tua carteira Ethereum que possui o NFT agora (0x... com 40 hex). Verificado on-chain via ownerOf."New value: +"A tua carteira Ethereum que possui o NFT agora."
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already mark this as a non-read-only, open-world, non-idempotent but non-destructive write; the description adds genuinely new behavior beyond them: no signature is requested, wallet control and sender authorization are NOT authenticated, and ownerOf is explicitly not proof of authorship. It also discloses that a public record is written and that permanent retention is not guaranteed, which is exactly the kind of trust caveat an agent needs before invoking a write. The parenthetical repeat of 'free; wallet control not authenticated' is redundant, keeping it just short of top marks.

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?

The key caveats (no signature, no wallet authentication, ownerOf not authorship) are front-loaded before the field requirements, which is the right order for a risky write. The trailing parenthetical duplicates points already made and could be cut, so it is efficient but not perfectly tight.

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 non-idempotent public write with no output schema and no nested objects, the description covers what the tool does, what it does not authenticate, and what is required. It omits what a successful call returns (an id, a record reference) and whether repeat calls create duplicate dedications, which an agent would want know given idempotentHint=false.

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 description coverage is 100%, so all four parameters are already documented, including format hints and the pointer to nft_catalogo for token_id. The description only restates the three required field names, adding no syntax, constraints, or meaning about 'mensagem' beyond what the schema provides, 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?

States a concrete verb and resource ('Publica uma dedicatoria') plus the mechanism (compares declared wallet against ownerOf on Ethereum), which is far more specific than the name alone. It does not name the obvious sibling nft_dedicar_simbolica, so an agent must infer the boundary between a plain dedication and a symbolic one.

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 prerequisites are stated implicitly by saying the service checks ownerOf and that token_id, wallet and nome are required, which tells an agent the caller must currently own the token. There is no explicit when-to-use/when-not or alternative routing to nft_dedicar_simbolica or nft_owner_atual, so selection guidance is only 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.