Auto-registo no programa de parceiros/referral (10% de comissao). O codigo e o teu proprio endereco Base. Requer address. (gratis)
| Name | Required | Description | Default |
|---|---|---|---|
| address | No | O teu endereco Base (0x... com 40 hex). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that the tool is free and requires an address, but does not describe side effects (e.g., whether it overwrites existing registration), error handling, or confirmation of success. For a registration tool, more behavioral context (like idempotency) is needed.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is concise, consisting of a few short phrases that convey the essential purpose and requirement. It is front-loaded with the main action. However, it could benefit from a more structured format (e.g., bullet points for prerequisites).
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the tool's simplicity (one parameter, no output schema), the description covers the basic purpose and parameter meaning. However, it lacks information about return values or success/failure indicators, which are important for an agent to confirm completion.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage with a single parameter 'address' described. The description adds value by explaining that 'O codigo e o teu proprio endereco Base' (the code is your own Base address), which clarifies the parameter's role beyond the schema's technical description.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool performs self-registration in a partner/referral program with a 10% commission, and mentions the address is used as the code. It is distinct from siblings like 'parceiro_estado' (check status) and 'doar' (donate). However, it could be more explicit about the specific program or what registration entails.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description only states that an address is required, but does not provide any guidance on when to use this tool versus alternatives, nor does it mention conditions for using it (e.g., not already registered). No explicit when-to-use or when-not-to-use information is given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools have distinct purposes, but nft_dedicar and nft_dedicar_simbolica are easily confused as both link a name to an NFT, differing mainly in ownership requirement and payment. Also, licenca_formal and receber_obra may be confused as both involve acquiring an artwork, though one is a paid license and the other a free gift; descriptions help clarify.
The tool names mix verb-first (doar, receber_obra) and noun-first patterns (nft_catalogo, parceiro_estado), and while they all use snake_case, there is no consistent verb_noun structure across the set. Some names use adjectives (nft_owner_atual, nft_dedicar_simbolica) making the pattern unpredictable.
With nine tools covering the collection, licensing, dedication, donation, and partner program, the server is well-scoped within the typical 3-15 range. Each tool serves a distinct function in the ecosystem.
The server covers the main interactions with the 0001sensations collection, including receiving, licensing, cataloguing, dedicating, and checking ownership. Minor gaps exist, such as no direct tool to browse the physical FISICA collection or manage licenses, but these are workaroundable via URLs or not essential.