Skip to main content
Glama

parceiro_registar

Cria ou confirma registo de referencia pelo endereco Base. Confere codigo e parceiro associado na base de dados antes de afirmar persistencia. Registo existente nao e recriado. Registo nao prova controlo da carteira, adopcao ou receita. Termos de comissao sao os declarados pelo servico; nao envia pagamentos. Requer address. (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": {
      "address": "<address>"
    },
    "name": "parceiro_registar"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesO teu endereco Base (0x... com 40 hex).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / address / maxLength
      Added value: +42
    • addedInput schema / properties / address / minLength
      Added value: +42
    • addedInput schema / properties / address / pattern
      Added value: +"^0x[0-9a-fA-F]{40}$"
    • addedInput schema / required
      Added value: +[
      +  "address"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / address / description
      Previous value: -"O teu endereco Base (0x... com 40 hex). Torna-se o teu codigo de referral e o teu endereco de recebimento."New value: +"O teu endereco Base (0x... com 40 hex)."
    • 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. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With annotations declaring readOnly=false, destructive=false and openWorld=true, the description still adds real value: it states that the service verifies code and partner in the database before asserting persistence, that an existing registration is not recreated, that no payments are sent, that commission terms come from the service, and that the call is free. One tension exists: 'Registo existente nao e recriado' reads as de-facto idempotency while idempotentHint is false, though this is a nuance about duplicate suppression rather than a hard contradiction.

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 action, with the preconditions and the caveats following in short sentences. A couple of sentences read as protective disclaimers ('nao prova controlo da carteira', 'Termos de comissao sao os declarados pelo servico'), but each still steers the agent away from a specific misuse, so little is wasted.

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 single-parameter, non-destructive mutation with no output schema, the definition covers the essential behavior: what is created/confirmed, what the service verifies internally, and what the result does not imply. It only leaves the concrete response shape (e.g., whether a confirmation code is returned) unspecified, which is minor at this complexity.

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 coverage is 100% and the schema already documents the single parameter with a 0x-prefixed 40-hex regex and length bounds. The description only restates 'Requer address' without adding format or semantic meaning beyond the schema, so the baseline of 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?

The opening sentence gives a concrete verb+resource pair ('Cria ou confirma registo de referencia pelo endereco Base') that an agent can act on, including the scope-limiting 'pelo endereco Base'. It does not name any sibling tool, so the agent must infer from the caveats ('nao prova controlo da carteira, adopcao ou receita') that this is not doar/licenca_formal/parceiro_estado.

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 is only implied: 'Requer address' and the disclaimer that registration does not prove wallet control, adoption or revenue tell the agent what this tool does NOT accomplish, which is useful negative guidance. However, no sentence says when to call it versus parceiro_estado (to read state) or the other siblings, and no prerequisites or follow-up steps are stated.

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.