Skip to main content
Glama

MNOGO DENEG — pay-per-call crypto & AI APIs (x402)

tool_ai_translate

[x402 paid: $0.020 USDC on Base] Translate text into any language (LLM). Body: {text, to}. tools/call returns the live payment challenge.

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": "tool_ai_translate"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description still discloses two materially useful traits: the fixed price ($0.020 USDC on Base via x402) and the fact that invoking it yields a live payment challenge. It does not explain the resulting call sequence (does the first call fail until paid?), whether the translation is returned in that same response, or any limits on input size, leaving the actual execution flow partly opaque.

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?

Three short clauses carry pricing, purpose, payload shape, and the payment handshake with no filler. Everything is front-loaded enough that an agent can act on the first reading.

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 zero-parameter, no-output-schema tool this covers purpose, cost model, and body fields, which is most of what an agent needs. It is still thin on the runtime contract: it is unclear what a successful response looks like or how the payment challenge is meant to be satisfied before a translation is returned.

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

Parameters4/5

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

The input schema declares an empty object with zero properties, so the description is the only source of parameter meaning, and it supplies it by naming the request body fields {text, to}. That is genuinely additive, though it stops short of clarifying whether 'to' accepts a language name or an ISO code, or whether 'text' has a length cap.

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 names a specific verb and resource ('Translate text into any language (LLM)'), which is unambiguous and distinguishable from nearby generation/summarization siblings such as tool_ai_chat or tool_ai_summarize. However, it never explicitly contrasts itself with those siblings, so the differentiation is only implicit.

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 guidance on when to choose this over tool_ai_chat (which could presumably translate too) or any other sibling, and no stated exclusions or prerequisites for the translation itself. The only procedural note ('tools/call returns the live payment challenge') explains a payment mechanic, not when the tool should be used.

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.

Resources