Skip to main content
Glama

ai_tools_embed

[$x402 pago por llamada] Vectoriza un texto con Qwen3-Embedding (Workers AI). El Neuron se gasta siempre despues del gate de pago x402 (api-core solo se alcanza via forwardToOrigin, que corre post-liquidacion en el Worker).

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": {
      "text": "<text>"
    },
    "name": "ai_tools_embed"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesTexto a vectorizar (1..2000 caracteres).
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/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 burden. It usefully discloses the x402 pay-per-call model and post-settlement flow, which is genuine behavioral context. However it never describes the actual return value (an embedding vector, its dimensions, or format), which is a notable gap for a tool with no output schema.

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?

The purpose is front-loaded but partially buried behind the bracketed '$x402 pago por llamada' tag. The second sentence spends considerable words on internal plumbing ('api-core solo se alcanza via forwardToOrigin, que corre post-liquidacion en el Worker') that is of marginal relevance to an agent deciding whether to call the tool.

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 tool with no output schema, the definition covers the payment mechanics but omits what the call returns (the embedding itself). An agent knows the cost model but not the result shape, leaving the completeness adequate but not thorough.

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 coverage is 100%, so both 'text' (1..2000 chars) and 'x_payment' (402 fallback behavior) are fully documented in the schema. The description adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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+resource ('Vectoriza un texto') and even names the model ('Qwen3-Embedding (Workers AI)'), which clearly distinguishes it from the transcribe and image_caption siblings. It does not explicitly contrast with siblings, but the embedding purpose is unambiguous.

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 tool versus alternatives, nor any preconditions beyond the payment context. The second sentence is about billing architecture, not about when/how an agent should invoke this versus, say, a text-processing sibling.

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