GadgetHumans API Hub

word_frequency

Rank the most frequent words in a text with counts and share of total, ignoring common stop words. 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": "word_frequency"
  }
}

Input Schema

Name	Required	Description	Default
`text`	Yes	Text to analyse
`limit`	No	How many words to return

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed3 schema fields changedNov 3, 2026

addedInput schema / properties / limit

Added value: +{
+  "description": "How many words to return",
+  "type": "integer"
+}

addedInput schema / properties / text

Added value: +{
+  "description": "Text to analyse",
+  "type": "string"
+}

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

AddedNov 2, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose real behavior: stop words are filtered out, and results include counts and share of total. However it omits case normalization, punctuation handling, whether output is sorted descending, and any default for limit, which an agent would want before calling.

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 with the core function front-loaded and the stop-word filtering next; 'Pure CPU, instant' earns its place by signaling latency and no external dependencies. Nothing is redundant.

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 two-parameter, no-annotation, no-output-schema tool, the description covers what it computes and roughly what comes back (counts plus share). The remaining gaps, case sensitivity and default limit, are minor but real.

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 both parameters are already documented at baseline 3. The description adds no meaning to 'limit' (no default, cap, or ordering assumption) and only hints at return shape, which is not a parameter.

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

Purpose4/5

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

The verb 'rank' plus the resource 'most frequent words' is specific, and 'with counts and share of total' pins down the output shape, which distinguishes it from sibling word_count. It stops short of naming the sibling or stating the comparison explicitly, so an agent must infer that word_count is the plain-total alternative.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of alternatives such as word_count or entity_count. The only contextual hint is the performance note 'Pure CPU, instant', which is not usage 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.