convertConvert an array of JSON objects to CSV (nested keys become dot-path columns) or CSV back to JSON. POST { direction: 'json-to-csv'|'csv-to-json', data }. Price: $0.002/call with credits key; free demo without (2KB input cap).
| Name | Required | Description | Default |
|---|---|---|---|
| data | Yes | Array of objects (json-to-csv) or CSV string (csv-to-json) | |
| direction | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the burden of disclosing behavioral traits. It adds useful context such as pricing ($0.002/call), free demo with 2KB cap, and nested-key flattening behavior. It does not mention output format details or error handling, but covers the key operational constraints.
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, front-loaded with the core conversion purpose, followed by the request format and pricing cap. Every word adds value, no fluff or repetition.
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 bidirectional converter tool, the description covers direction, data format, nested key handling, and pricing constraints. It lacks explicit output format and error scenarios, but given the tool's simplicity and the absence of an output schema, it is reasonably complete.
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 covers direction with an enum and data with a type description, but only 50% of parameters have explicit descriptions. The description adds the dot-path column behavior for json-to-csv and reinforces the POST structure, yet it does not fully compensate for the missing direction description and edge-case parameter behaviors.
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 it converts between JSON and CSV, with specific direction handling and nested-key dot-path behavior. This is a precise verb+resource pairing that distinguishes it from sibling conversion tools like html_to_markdown.
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 when to use the tool by specifying the two conversion modes and giving a POST example. It does not explicitly name alternatives or exclusions, but the context of JSON/CSV conversion is clear, and pricing/demo notes add practical guidance on when paid vs free usage applies.
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 unique, non-overlapping purpose. Even closely related tools like html_to_markdown and markdown_to_html are clearly inverses, and read_page combines fetching and conversion, so no two tools could be confused for the same task.
All names are lowercase with underscores, maintaining a consistent syntactic style. However, there is no strict verb-noun pattern: some names are nouns (cron, diff, qr, timezone), others are verbs (convert, extract), and word order varies (email_verify vs validate_ids), which is a minor deviation.
With 13 tools, the count is well within the ideal 3-15 range. Each tool provides a distinct paid utility, and none feel redundant or out of place for a general-purpose vending machine API.
The tool surface covers a broad range of common utilities—format conversion, validation, extraction, formatting, and time handling. There are minor gaps like missing YAML conversion or raw HTML fetching, but these are not critical for the server's stated purpose as a collection of paid utilities.