Skip to main content
Glama

minia2a — hosted x402 API marketplace (HTTP)

x402-avg-word-length

Avg Word Length: Average word length in characters. Takes text (alias input). Returns the average length as result. 🆓 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-avg-word-length"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNo
inputNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • removedInput schema / properties / input / description
      Removed value: -"Input to process"
    • removedInput schema / properties / text / description
      Removed value: -"Text to process"
  2. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It discloses that the tool returns an average length and mentions a signed-wallet free-trial limit, but it does not define what counts as a word, how punctuation/numbers are handled, or the output type and precision.

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?

The description is short and front-loaded, with no wasted paragraphs. The leading 'Avg Word Length:' restates the name slightly redundantly, but the remaining sentences are efficient.

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 two-parameter computation, the description covers the basic purpose, alias relationship, output summary, and trial auth context. However, it omits the word-tokenization definition and output precision, which are important for interpreting the average correctly.

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 0%, so the description must compensate. It usefully identifies 'text' and 'input' as aliases, but it does not clarify whether one is required, what happens if both are supplied, or how empty strings are treated.

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 computation: average word length in characters, returning the average as a result. The purpose is clear, but it does not explicitly differentiate this from sibling tools such as word-count or average-sentence-length.

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 explicit guidance on when to use this tool versus alternatives like word-count or average-sentence-length. The intended use is implied by the name, but no conditions, exclusions, or alternative routing are provided.

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.