Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-levenshtein-distance

Levenshtein Distance: Distance between levenshtein. 🆓 5 free trial calls per signed wallet

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "x402-levenshtein-distance"
  }
}

Input Schema

NameRequiredDescriptionDefault
aNo
bNo
textNo
otherNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • removedInput schema / properties / a / description
      Removed value: -"A to process"
    • removedInput schema / properties / b / description
      Removed value: -"B to process"
    • removedInput schema / properties / other / description
      Removed value: -"Other to process"
    • removedInput schema / properties / text / description
      Removed value: -"Text to process"
  2. First observed

TDQS

D1.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It does disclose one real behavioral trait — a metered paywall of 5 free trial calls per signed wallet — but says nothing about output shape, error behavior, or whether inputs are case/punctuation sensitive.

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

Conciseness3/5

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

Very short and front-loaded with the tool name, but the second clause is a wasteful restatement and the emoji-plus-paywall line mixes unrelated concerns into the purpose statement.

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

Completeness1/5

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

For a tool with four unlabeled parameters, no annotations, and no output schema, the definition is critically incomplete: an agent has no basis for choosing which two arguments to send or what a valid call looks like.

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

Parameters1/5

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

Schema description coverage is 0% and the description gives no parameter meaning whatsoever. With four undocumented string parameters named a, b, text, and other, an agent cannot tell whether a/b form the compared pair and text/other are aliases or a second mode — this is the exact case where the description must compensate and does not.

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

Purpose2/5

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

"Levenshtein Distance: Distance between levenshtein" is a tautology that restates the tool name without saying what it computes (edit distance between two strings) or what it returns. An agent that already knows the algorithm can guess, but the description itself adds nothing.

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 guidance at all — no hint about choosing this over the near-identical sibling x402-levenshtein or the other similarity tools (x402-text-similarity, x402-jaccard-similarity, x402-hamming). The only extra text is a pricing note, 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.