Skip to main content
Glama

Text To Embedding

text_to_embedding

Generate text embeddings using AI models.

Converts text into vector embeddings for semantic search, similarity comparison, and other NLP tasks. Accepts a single string or a list of strings.


Available models:

  • Bge_M3_FP16: ≤8192 tokens/input

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_to_embedding"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesText string or list of text strings to embed
modelNoEmbedding model name (e.g., 'Bge_M3_FP16')Bge_M3_FP16
webhook_urlNoHTTPS URL for deAPI to call when this job finishes. Notifies your own systems; the tool still returns the result here
webhook_secretNo32-255 char key deAPI signs the callback with (HMAC-SHA256). Needs webhook_url. A secret given in chat stays in the transcript
return_result_in_responseNoReturn embedding inline

Output 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, the description must carry the full burden; it usefully discloses the available model and an 8192-token/input limit, which is real behavioral context. However, it never clarifies whether execution is synchronous or creates a job (the presence of webhook parameters and a check_job_status sibling makes this ambiguous), nor does it mention cost or rate behavior.

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?

Two tight purpose sentences followed by a short model list; the core action is front-loaded and there is little filler. The trailing bullet is minimal but earns its place by giving a token limit.

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?

An output schema exists, so return values need not be explained, and the description covers input shape, intended uses, and a model constraint. The remaining gap is the async/webhook lifecycle and the relationship to the pricing sibling, which an agent would need in order to choose 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 coverage is 100%, so parameters are already well documented, and the description largely repeats the input shape ('single string or a list of strings'). It adds the model default/availability and the token constraint, but says nothing about webhook or return_result_in_response semantics beyond the schema.

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 verb+resource ('Generate text embeddings') and clarifies input shape ('Accepts a single string or a list of strings') plus use cases. It does not distinguish itself from the obvious sibling 'text_to_embedding_price', so an agent cannot tell from the description alone which of the two to pick.

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?

Usage is implied through purpose ('semantic search, similarity comparison, and other NLP tasks') but there is no explicit when-to-use versus alternatives such as the price-estimation sibling or job-status tooling. No exclusions or prerequisites are stated.

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.