GadgetHumans API Hub

text_replace

Replace text across a block and report the number of replacements. 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": "text_replace"
  }
}

Input Schema

Name	Required	Description
`find`	No	Search string
`text`	Yes	Text to edit
`replace`	No	Replacement

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 8, 2026
RemovedNov 6, 2026

Changed4 schema fields changedNov 3, 2026

addedInput schema / properties / find

Added value: +{
+  "description": "Search string",
+  "type": "string"
+}

addedInput schema / properties / replace

Added value: +{
+  "description": "Replacement",
+  "type": "string"
+}

addedInput schema / properties / text

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

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

AddedNov 2, 2026

TDQS

B3.3/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 burden of behavioral disclosure. It usefully says the tool is pure CPU and instant and that it reports the replacement count, but it does not explain whether matching is literal or regex, case-sensitive, all occurrences versus first occurrence, or what happens when the find string is absent.

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, front-loaded with the core operation, and includes the useful performance/return-count context without unnecessary wording.

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

Completeness3/5

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

For a simple three-parameter text tool with no annotations and no output schema, the description covers the basic purpose and mentions the return count. However, it omits important matching semantics such as literal versus regex behavior and case sensitivity, so it is only minimally complete.

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 schema already documents all three parameters. The description adds no additional meaning about find, text, or replace beyond what the parameter names and schema descriptions provide, making the baseline 3 appropriate.

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 description states a specific verb and resource: replace text across a block and report the number of replacements. This is clear enough to identify the operation, but it does not differentiate the tool from nearby text-manipulation siblings such as text_diff, regex_test, or truncate.

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?

The description gives no explicit when-to-use guidance, prerequisites, exclusions, or alternative tools. An agent can infer that it is for find-and-replace work, but there is no routing help among the many text-related siblings.

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.