Skip to main content
Glama

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

tool_ai_keywords

[x402 paid: $0.020 USDC on Base] Extract keywords, named entities and topics from text as JSON (LLM). Body: {text}. 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_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose two important things: the $0.020 USDC x402 price on Base and that tools/call returns a live payment challenge rather than a result. However, it does not explain how to satisfy that challenge, what happens on payment failure, any input size limits, or the shape of the successful JSON response.

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?

Very compact and front-loaded: price tag, then the action, then the call-flow caveat. Three short sentences with no filler. The bracketed payment metadata slightly interrupts the purpose statement, which is the only structural nit.

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?

No annotations and no output schema, so the description needs to do more work than it does. It covers purpose, the required text body, and the payment challenge, but leaves the response structure, the payment completion steps, and failure behavior undocumented for a tool that is both paid and non-standard in its call flow.

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 zero properties, yet the description reveals the required input via 'Body: {text}', which is essential — without it an agent would have nothing to send. That is real added meaning beyond the schema, though it gives no format, length, or language guidance for the text field.

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?

States a specific verb and resource: 'Extract keywords, named entities and topics from text as JSON (LLM).' That is concrete work an agent can match to a task, and it is implicitly distinct from siblings such as tool_ai_summarize or tool_ai_translate. It stops short of explicitly contrasting itself with those siblings, so a 4 rather than a 5.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no named alternative for extraction tasks. Usage is only implied by the stated purpose — an agent must infer on its own that this is the tool for entity/keyword extraction rather than summarization or chat.

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