GadgetHumans API Hub

ini_to_json

Convert INI or config-style key/value files into JSON, with each section as an object. Pure CPU, instant.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "ini": "<ini>"
    },
    "name": "ini_to_json"
  }
}

Input Schema

Name	Required	Description	Default
`ini`	Yes	INI text to convert

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / ini

Added value: +{
+  "description": "INI text to convert",
+  "type": "string"
+}

addedInput schema / required
```
Added value: +[
+  "ini"
+]
```

AddedNov 2, 2026

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the operation is pure CPU and instant and that sections become objects, but it omits behavior for malformed input, duplicate keys, or config-style edge cases.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences are front-loaded with the core action and output shape. The performance note is brief and no wording is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple one-parameter conversion tool with no output schema, the description gives the essential purpose and a hint about the returned JSON structure. It is close to complete, though edge-case behavior is not covered.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the single parameter is already documented as 'INI text to convert.' The description adds no parameter-specific syntax, format, or constraints beyond what the schema already says.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: convert INI or config-style key/value files into JSON. It also specifies the output shape, with each section as an object, and the input format clearly distinguishes it from siblings such as toml_to_json or xml_to_json.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The input format implies when the tool is useful, but there is no explicit when-to-use or when-not-to-use guidance and no named alternatives among the many sibling converters. The usage is inferable but not spelled out.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All GadgetHumans API Hub tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.