Reverse engineering. An agent can generate many realistic credential-style files on its own, so limit its scope to a test folder and require a human review step before any file leaves the environment.
Who it is forAn agent builder who wants an agent to request synthetic education documents by country through a standard MCP connection.
The problemAgents need a callable tool with discoverable options, and building one for thirteen countries from scratch is slow.
The outcomeAn MCP-connected agent that discovers countries and schools, then generates documents on request.
What you need first
- Python 3.10 or newer
- pip, or uv for the uvx route
- An MCP client that speaks stdio, such as the clients named in the README
- A test environment with synthetic data only
Steps
- Install the wheel with
pip install dist/yowes_doc_generator-0.1.0-py3-none-any.whlor install from source withpip install -e . - Run the server with
uvx --from . yowes-mcp - Register the stdio server in your agent runtime's MCP settings
- Let the agent call list_countries_tool and list_schools before any generation call
- Review each generated file in output/ before the agent passes it to any downstream step
Prompt for your agent
Connect to the yowes MCP server from the hirotomasato/yowes repo over stdio. Call list_countries_tool, then list_schools for <country code>, and report the country codes and school names found. Expected output: a list of valid options with no documents created until asked. Verify that every returned country code matches one of the 13 in the README table.
Caveat. The README names the tools list_countries_tool and list_schools but does not document the generation tool's parameters, so check the exposed tool schema before writing agent calls.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page