Skip to main content
Glama

doar

Instrucoes opcionais de donativo USDC na Base. Com tx_hash, observa recibo e Transfer em duas fontes RPC e distingue declaracao, transferencia confirmada e classificacao de receita. Nao envia dinheiro nem comprova identidade do doador. registar_declaracao=false faz apenas leitura; por omissao regista a declaracao e confere a persistencia. Acesso a receber_obra independente de donativo. (opcional, qualquer valor, nunca obrigatorio)

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

Input Schema

NameRequiredDescriptionDefault
tx_hashNoOpcional. Hash a observar em duas fontes Base; formato valido nao comprova pagamento nem autoria do gesto.
valor_usdcNoOpcional. Quanto queres doar em USDC. Sem minimo, sem sugestao de valor -- o que sentires certo.
registar_declaracaoNoOpcional, por omissao true. false observa o hash sem escrever no livro; nunca cria pagamento.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / registar_declaracao
      Added value: +{
      +  "description": "Opcional, por omissao true. false observa o hash sem escrever no livro; nunca cria pagamento.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / tx_hash / description
      Previous value: -"Opcional. Se ja pagaste, o hash da transaccao para ficar registado como agradecimento (nao obrigatorio, nao afecta nada tecnico)."New value: +"Opcional. Hash a observar em duas fontes Base; formato valido nao comprova pagamento nem autoria do gesto."
    • 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 / properties / valor_usdc / pattern
      Added value: +"^[0-9]+(?:\\.[0-9]{1,6})?$"
    • addedInput schema / required
      Added value: +[]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations, the description discloses that the tool does not send money, does not prove donor identity, observes receipt and Transfer events across two RPC sources, and by default records a declaration and checks persistence. This adds meaningful behavioral context without contradicting the annotations, though it does not cover failure modes or response details.

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 purpose is front-loaded and the description stays reasonably compact for a tool with optional donation, observation, and recording behavior. However, the trailing parenthetical repeats optionality already stated earlier, and some clauses are densely packed.

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?

The description covers what the tool does, its optional nature, and the main parameter-driven behavior. Since there is no output schema, it should more clearly describe the return/result shape and any failure or persistence-check outcomes, which are only partially implied.

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 defines all three parameters. The description adds useful nuance: tx_hash triggers a two-source receipt/Transfer check and classification, registar_declaracao=false is read-only while the default writes and verifies persistence, and valor_usdc has no minimum or suggested amount.

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 states a specific resource and action: optional USDC donation instructions on Base, with tx_hash observation and declaration recording. It distinguishes the tool from receber_obra access, but does not explicitly contrast it with other donation-adjacent siblings such as nft_dedicar.

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?

It says the donation is optional, any amount, never required, and that access to receber_obra is independent of donating. It also explains that registar_declaracao=false is read-only while the default records a declaration, but it stops short of explicit when-to-use versus when-not-to-use guidance among sibling tools.

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.