Look up any CC0 creator, collection, or work by name or slug — provenance, creator, license, on-chain pointers (collection contract addresses / chains / OpenSea), and the full CC0 body. The agentic read API over the largest machine-readable CC0 database. Synchronous JSON (no polling). [PAID: $0.01 USDC per call via x402]
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Name or slug of a CC0 creator, collection, or work (e.g. 'sartoshi', 'mfers', 'xcopy'). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description explicitly states it's a read API, synchronous, and paid ($0.01 USDC per call). It does not contradict any annotations (none provided). However, it does not specify if there are rate limits or authentication needs beyond payment.
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 front-loaded with the essential purpose and output details. It is slightly verbose but every sentence adds value (purpose, positioning, mode, pricing). Could be shortened slightly without losing clarity.
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 one simple parameter and no output schema, the description fully explains what the tool returns (provenance, creator, license, etc.) and how it works (synchronous, paid). No gaps for a lookup tool.
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 single parameter 'query' is well-explained with examples, and schema coverage is 100%. The description adds meaningful context beyond the schema.
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 resource (CC0 creators, collections, works), the action (look up), and what information is returned (provenance, license, on-chain pointers, etc.), distinguishing it from sibling tools like market, search, and verify.
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 implies it's the primary lookup tool for CC0 entities, mentioning synchronous JSON and paid model. However, it does not explicitly contrast with siblings (e.g., when to use search instead), so some guidance is missing.
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.
