GadgetHumans API Hub

nato_phonetic

Spell text with the NATO phonetic alphabet, or decode the words back to letters. 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": {
      "text": "<text>"
    },
    "name": "nato_phonetic"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	Text or phonetic words
`decode`	No	Decode phonetic words

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed3 schema fields changedNov 3, 2026

addedInput schema / properties / decode

Added value: +{
+  "description": "Decode phonetic words",
+  "type": "boolean"
+}

addedInput schema / properties / text

Added value: +{
+  "description": "Text or phonetic words",
+  "type": "string"
+}

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

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 supplied, so the description carries the full disclosure burden. It adds useful context by stating 'Pure CPU, instant,' but it does not describe input-handling behavior, such as how invalid characters, spacing, or case are treated during encode/decode.

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?

The description is two short sentences and front-loads both operations immediately. There is no unnecessary wording, and the performance note is compact.

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 two-parameter text transformation with a fully described schema and no output schema, the description is sufficiently complete. It identifies the operations and performance profile, though it could mention input assumptions for decode mode.

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 baseline is 3. The description reinforces that 'text' is the text or phonetic words to process and that decoding is selected through the decode behavior, but it does not add substantial parameter semantics beyond the schema descriptions.

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: spell text with the NATO phonetic alphabet or decode phonetic words back to letters. This clearly distinguishes the tool from generic encoders and from siblings such as morse or base64 because the NATO alphabet is explicitly named.

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 description implies the two usage modes (encode via text, decode via the decode flag), so an agent can infer how to call it. However, it gives no explicit when-to-use guidance versus alternatives and no exclusions or edge-case guidance.

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.