MoneyTools x402 agent toolkit

Text similarity / dedupe

text_similarity

Read-onlyIdempotent

Compare two texts: bag-of-words cosine, word Jaccard, Levenshtein distance/ratio and a near-duplicate verdict. Lexical, no embeddings. Free: 10 calls/day; then $0.001/call via x402 (MCP params._meta["x402/payment"] or HTTP) or X-API-Key credits. [served by tools.moneytools.dev]

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": {
      "a": "<a>",
      "b": "<b>"
    },
    "name": "text_similarity"
  }
}

Input Schema

Name	Required	Description	Default
`a`	Yes	text A
`b`	Yes	text B

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description adds genuinely non-redundant behavior: it is purely lexical with no embeddings, and it discloses rate limits (10 calls/day) and the payment paths (x402 via params._meta or HTTP, or X-API-Key credits). It does not explain scoring thresholds for the near-duplicate verdict, which is the one behavioral detail an agent would still want.

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

Conciseness4/5

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

Purpose and algorithmic scope are front-loaded in the first two sentences with zero filler. The third sentence packs billing and payment mechanics densely; it is useful for cost planning but is the least essential part and slightly crowds out task guidance.

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

Completeness5/5

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

An output schema exists, so return values need not be spelled out, and the description still names what is computed. With only two string parameters, a declared safety profile, and the access/payment model fully stated, nothing an agent needs in order to invoke it correctly is missing.

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?

Both parameters are fully described in the schema (100% coverage, with examples), so the schema already carries the semantic load. The description adds nothing about formatting, length limits, or asymmetry between A and B, so baseline 3 applies.

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?

States a specific verb and resource ("Compare two texts") and enumerates the exact outputs: bag-of-words cosine, word Jaccard, Levenshtein distance/ratio, and a near-duplicate verdict. The clause "Lexical, no embeddings" further scopes it against semantic-similarity alternatives, so an agent can distinguish it from text_diff or text_stats without opening a schema.

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 title's "dedupe" hint plus the "near-duplicate verdict" output imply the use case (deduplication / comparing two strings), but the description never states when to prefer this over text_diff or text_stats, nor any exclusions. The only explicit conditions given are commercial (free tier limit, then paid), not task-oriented.

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

All MoneyTools x402 agent toolkit 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.

Resources

Need Help?