Skip to main content
Glama

APEX AI, LLM, Embeddings, OCR & Media

Text embeddings

text_embeddings
Read-onlyIdempotent

OpenAI-compatible BGE text embeddings for RAG and semantic search (bge-large-en-v1.5 1024d default, bge-base-en-v1.5, bge-small-en-v1.5, bge-m3 multilingual). $0.001 per call over x402 (Base, Solana or X1) or X-API-Key. Call once without payment for terms, then pass payment.

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": {
      "input": "<input>"
    },
    "name": "text_embeddings"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesText string or array of up to 32 strings (<=16,000 chars total) to embed.
modelNoOptional model id (default bge-large-en-v1.5): bge-large-en-v1.5, bge-base-en-v1.5, bge-small-en-v1.5, bge-m3.
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context: cost per call ($0.001), accepted payment rails (Base, Solana, X1) and the X-API-Key alternative. It does not mention rate limits, batching behavior across calls, or error/settlement behavior when payment is invalid, so it stays at 3.

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 dense sentences: purpose and models first, price and payment rails second, call sequence last. No filler, and the pricing/payment constraint is front-loaded ahead of the call instructions.

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

Completeness4/5

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

No output schema exists, and the description gives partial return information via dimensionality (1024d) but does not state the response shape or how the array maps to the input list. For a 3-parameter inference endpoint whose annotations cover safety and whose schema is fully documented, this is nearly complete, with only the return-format gap remaining.

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?

Schema description coverage is 100%, so the baseline is 3. The description nonetheless adds real meaning beyond the schema: the default model's output dimensionality (1024d), which models are multilingual, and the protocol-level intent of `payment` (terms on first call, then a signed payload), which the schema only names as PAYMENT-SIGNATURE.

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

Purpose5/5

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

States a specific verb+resource ('BGE text embeddings'), names the model family and the concrete use cases (RAG, semantic search), and lists the selectable model variants. An agent can distinguish this from sibling media tools like pdf_text or text_to_speech without opening the schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives an explicit two-step operating procedure — call once without `payment` to receive terms, then pass `payment` — which is the key when-to-do-what guidance for this tool. It stops short of naming alternatives or when-not-to-use conditions, so it is a strong 4 rather than a 5.

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.