make_qrAny text or URL → a QR code PNG you can embed or download. Stateless URL form: https://ainetcafe.com/i/qr/
| Name | Required | Description | Default |
|---|---|---|---|
| text | Yes | The text or URL to encode. |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds value by specifying the output is a downloadable/embeddable PNG and providing the stateless URL pattern, beyond what annotations convey.
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 two sentences long, front-loads the core functionality, and includes a useful URL example. Every sentence earns its place with zero redundancy.
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 one-parameter tool with an output schema, the description covers everything needed: purpose, output format, and an alternative access method. No significant gaps remain.
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 the 'text' parameter well described as 'The text or URL to encode.' The description reinforces that any text works but does not add substantial new meaning beyond the schema, so 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?
The description explicitly states the tool converts any text or URL into a QR code PNG, with a clear verb and resource. It distinguishes itself from sibling tools (e.g., diff_text, json_format) by its specific function and mentions the output format.
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 clearly implies when to use the tool (whenever a QR code is needed) and mentions the stateless URL form as an alternative delivery method. It does not explicitly name exclusions or alternatives, but context with siblings makes the usage obvious.
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 clear, separate purposes: diff, redact, regex, JWT, SQL, timezone, units, QR, screenshot. The main overlap is between json_format and validate_json, since both parse and validate JSON, though their outputs differ enough to be workable.
The majority follow a clear snake_case verb_noun or noun_verb pattern like diff_text, transpile_sql, and timezone_convert. sql_from_description and what_can_you_do break the pattern, but the rest is predictable and readable.
14 tools is well-scoped for a general-purpose developer utility server. Each tool covers a distinct practical need, and the count does not feel bloated for the breadth of features offered.
The toolkit covers a broad range of everyday dev utilities: text diffing, redaction, regex, JSON/YAML, SQL, time, units, JWT, QR, and screenshots. Some common basics like base64, hashing, or URL encoding could be useful additions, but the surface is complete enough for its stated purpose.