Skip to main content
Glama

nft_dedicar_simbolica

Sem precisares de possuir o NFT: escolhe uma peca livre das 65, paga directamente ao artista, e o teu nome fica ligado a ela para sempre no registo publico. (0.618 USDC via x402)

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

Input Schema

NameRequiredDescriptionDefault
nomeYesComo queres ser lembrado. Max 80 caracteres.
tx_hashNoOpcional. Hash da transaccao apos pagar 0.618 USDC na Base para a carteira sagrada. Omitir para receber as instrucoes de pagamento.
mensagemNoOpcional, max 400 caracteres.
token_idYesNumero do token NFT livre (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 / tx_hash / maxLength
      Added value: +66
    • addedInput schema / properties / tx_hash / minLength
      Added value: +66
    • addedInput schema / properties / tx_hash / pattern
      Added value: +"^0x[0-9a-fA-F]{64}$"
    • addedInput schema / required
      Added value: +[
      +  "token_id",
      +  "nome"
      +]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare it is a non-readonly, non-idempotent, open-world write. The description adds material behaviour: payment of 0.618 USDC via x402 goes directly to the artist, the attribution is permanent in a public registry ('para sempre no registo publico'), and no NFT ownership is required. That permanence cue is the most important behavioural fact and is not in the annotations; only the post-payment retrieval flow is left unexplained.

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?

One front-loaded sentence establishes the no-ownership condition, the choice of a free piece and the permanence outcome, with the price appended as a short parenthetical. Nothing is padding, though the trailing '(0.618 USDC via x402)' is slightly detached from the payment mechanics it refers to.

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

Completeness3/5

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

For a monetary, permanent, non-idempotent write with no output schema, the description covers cost, payment channel, permanence and the no-ownership prerequisite. It omits two things an agent needs: how to find free pieces (only the schema mentions nft_catalogo) and how this differs from the near-identically named nft_dedicar.

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?

Schema coverage is 100%, so the schema already documents nome, mensagem, token_id and tx_hash, giving a baseline of 3. The description adds meaning the schema lacks: only 65 pieces exist and they must be free ('peca livre'), and the 0.618 USDC via x402 price contextualises what tx_hash actually represents. It stops short of detailing the payment-then-retry sequence.

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 gives a specific verb ('dedicar' / 'escolhe uma peca livre') and resource (one of 65 free NFT pieces), plus a key qualifier: 'Sem precisares de possuir o NFT'. That makes the action legible. It never distinguishes itself from the sibling 'nft_dedicar', whose name is nearly identical, so an agent cannot route between the two on description alone.

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 context is implied by 'Sem precisares de possuir o NFT' (use when you don't own the piece and want to attach your name) and the schema note about omitting tx_hash to receive payment instructions. There are no explicit when-not conditions and no named alternative such as nft_dedicar or licenca_formal, leaving the sibling choice ambiguous.

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.