Skip to main content
Glama

parceiro_estado

Read-onlyIdempotent

Consulta o estado do parceiro e confere a existencia do registo associado. Saldos e comissoes sao valores declarados pelo servico, sem verificacao de liquidacao on-chain. Nao cria parceiro nem prova adopcao. Requer code. (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": {
      "code": "<code>"
    },
    "name": "parceiro_estado"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesO endereco Base usado no registo.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / code / maxLength
      Added value: +42
    • addedInput schema / properties / code / minLength
      Added value: +42
    • addedInput schema / properties / code / pattern
      Added value: +"^0x[0-9a-fA-F]{40}$"
    • addedInput schema / required
      Added value: +[
      +  "code"
      +]
  2. Changed3 schema fields changed
    • changedInput schema / properties / code / description
      Previous value: -"O endereco Base usado no registo, para consultar o saldo."New value: +"O endereco Base usado no registo."
    • 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

A4.1/5.0
Behavior5/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the description's real contribution is the data-provenance caveat: balances and commissions are service-declared values with no on-chain settlement verification. That is a non-obvious trust limitation an agent could not infer from structured fields, and "(gratis)" adds a cost signal as well.

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?

Sentences are short and front-loaded: purpose first, then the trust caveat, then the exclusions, then the required parameter. "Requer code" is mildly redundant given the required field in the schema, but nothing else 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 one-parameter read-only lookup with no output schema, the description covers purpose, prerequisite, exclusions, and the trustworthiness of returned balances. It could have sketched what the returned status/record looks like, but the essential calling information is present.

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% and the single `code` parameter already documents its format (Base address, 0x + 40 hex) and its meaning. The description only restates "Requer code", adding no syntax, format, or sourcing 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.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

"Consulta o estado do parceiro e confere a existencia do registo associado" names a specific verb (consulta/confere) and resource (estado do parceiro, registo), so the agent knows exactly what it retrieves. It also negates a sibling action ("Nao cria parceiro"), which implicitly separates it from parceiro_registar, though it never names that sibling explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives a clear when-not ("Nao cria parceiro nem prova adopcao") and a hard prerequisite ("Requer code"), which is enough to route an agent away from the registration tool. It stops short of an explicit "use this when you need X instead of Y" statement naming the alternative.

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.