Skip to main content
Glama

receber_obra

Read-only

Consulta gratuitamente um registo do arquivo historico dos 65 NFTs 0001sensations (Ethereum, 2021), por nome ou token_id. Devolve metadados guardados e URL de imagem; nao le a cadeia nem verifica os bytes nesta chamada. token_id nao e numero fisico. Nao transfere NFT, obra fisica ou direitos de utilizacao. Para numeros fisicos e previews verificados, usa o MCP da Casa indicado na resposta. (gratis, sempre)

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

Input Schema

NameRequiredDescriptionDefault
obraNoOpcional. Nome ou token_id do arquivo NFT historico, nunca numero da obra fisica. Sem isto, escolhe-se um registo ao acaso.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / required
      Added value: +[]
  2. Changed2 schema fields changed
    • changedInput schema / properties / obra / description
      Previous value: -"Opcional. Nome ou token_id de uma obra especifica. Sem isto, recebes uma obra escolhida por quem pede primeiro ou por acaso."New value: +"Opcional. Nome ou token_id do arquivo NFT historico, nunca numero da obra fisica. Sem isto, escolhe-se um registo ao acaso."
    • addedInput schema / properties / obra / maxLength
      Added value: +200
  3. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark it readOnly and non-destructive; the description adds real context beyond that: it returns stored metadata plus an image URL, does not touch the chain or verify bytes, and grants no NFT, physical work or usage rights. It also explains the non-idempotent annotation indirectly via the random-record fallback in the schema, though it never says what happens on a failed lookup.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and the non-capabilities are front-loaded, but the text is dense and repeats the free-of-charge point ('Consulta gratuitamente' and '(grátis, sempre)'), and the parenthetical trailer adds little. Nothing is truly wasted, but the redundancy costs a point.

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 optional-parameter read with no output schema, the description covers what comes back (stored metadata and image URL), what the input is not, and what the tool refuses to do. Only edge behaviour on a miss or a malformed name is left unstated.

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 baseline is 3, but the description adds meaning: the input accepts a name or token_id, and token_id is explicitly not a physical work number. The random-selection default when omitted is spelled out in the schema rather than the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

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

States a specific verb and resource: a free lookup of one record from the historical archive of the 65 0001sensations NFTs (Ethereum, 2021), by name or token_id. An agent can tell this apart from catalogue- or ownership-oriented siblings without opening the schema.

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?

Gives clear conditions: use it for archive records by name or token_id, and note that it neither reads the chain nor verifies bytes, and that physical numbers and verified previews belong elsewhere. The alternative is only pointed at indirectly ('o MCP da Casa indicado na resposta') rather than named among the siblings, so the routing is slightly weaker than it could be.

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.