Query the mfer lore archive (history, culture, community) by mfergpt. Re-brokered over x402 — pass your search as the prompt. [PAID: $0.025 USDC per call via x402]
| Name | Required | Description | Default |
|---|---|---|---|
| prompt | Yes | Input prompt for this service. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must convey behavioral traits. It discloses that calls are paid ($0.025 USDC) and re-brokered over x402, which is useful. However, it does not confirm whether the tool is read-only, idempotent, or has side effects, leaving uncertainty about its operational impact.
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?
Two sentences efficiently convey purpose ('query the mfer lore archive'), usage ('pass your search as the prompt'), and cost ('PAID: $0.025 USDC per call'). No superfluous text; every sentence serves a purpose.
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?
Despite having only one parameter and no output schema, the description does not mention what the tool returns (e.g., lore texts, summaries). This omission forces the agent to guess the response format, reducing completeness.
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?
Schema coverage is 100% with one parameter 'prompt' described generically as 'Input prompt'. The description adds value by specifying that the prompt should be a 'search' query, clarifying the intended usage beyond the schema's minimal 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 queries the 'mfer lore archive' for history, culture, and community, which is a specific and distinct purpose. However, it does not explicitly differentiate from sibling tools like 'mfergpt-ask' or 'mfergpt-mferfy', leaving some ambiguity about when to use this particular tool over others.
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?
No guidance is provided on when to use this tool versus alternatives. The description only instructs to 'pass your search as the prompt', but does not clarify prerequisites, typical use cases, or scenarios where another sibling tool would be more appropriate.
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.
