License oracle: pass a contract address, get whether it's a documented CC0 work + full provenance (creator, chain, standard, supply, sources). The 'is this safe to reuse?' check before touching on-chain art. Synchronous JSON, $0.01/check. [PAID: $0.01 USDC per call via x402]
| Name | Required | Description | Default |
|---|---|---|---|
| contract | Yes | EVM contract address (0x...) to check for documented CC0 status. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description carries full burden. Discloses synchronous JSON response, cost ($0.01/check), and payment method (x402). Does not specify error handling for invalid addresses, but sufficiently transparent for a simple query.
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?
Three sentences covering purpose, use case, and technical details. No wasted words, front-loaded with core functionality.
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?
For a simple lookup tool with one parameter and no output schema, description adequately explains inputs, outputs (CC0 status + provenance), and behavior (synchronous, paid). Minor gap: no mention of handling non-CC0 or unknown contracts.
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?
Single parameter 'contract' is described in schema as 'EVM contract address...'. Description adds 'to check for documented CC0 status' but adds little beyond schema. With 100% schema coverage, baseline 3 is appropriate.
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?
Clearly states it's a license oracle that checks if a contract address is a documented CC0 work and returns full provenance. Distinguished from sibling tools like cc0pedia-search by focusing on address-based verification for reuse safety.
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?
Provides explicit use case: 'The 'is this safe to reuse?' check before touching on-chain art.' Implies when to use, but lacks explicit when-not-to-use or alternatives. Mentions paid nature.
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.
Each tool has a clearly distinct purpose: data query (cc0pedia*), market data, daily brief, art generation by specific artists, mfergpt interactions, and random card generation. No two tools overlap in functionality.
Names are consistently lowercase with hyphens, and within each subgroup (e.g., `-gen` for generation, `cc0pedia-` for data tools), patterns are clear. However, there is no single verb_noun pattern across all tools, with some being proper names (cc0-daily-brief) or suffixed with `-ask`, `-lore`, etc.
14 tools is well-scoped for the server's purpose, covering CC0 data retrieval, art generation, and a chatbot. Each tool adds distinct value without overwhelming the set.
The server covers core operations: CC0 data lookup, search, verify, market, daily brief; four distinct art generation styles; mfergpt Q&A, lore, and image transformation; plus random card generation. A minor gap is the lack of a tool to list available art styles or a general-purpose CC0 art explorer, but essential workflows are present.
