Skip to main content
Glama

openai_create_embedding

Convert text into numerical vector representations for semantic search, similarity comparison, and machine learning tasks using OpenAI embedding models.

Instructions

Create text embeddings using OpenAI embedding models via AceDataCloud.

Converts text into numerical vector representations that can be used for
semantic search, text similarity, clustering, and other ML tasks.

Use this when:
- You need to compare semantic similarity between texts
- You want to build a semantic search system
- You need vector representations for machine learning

Returns:
    JSON response containing the embedding vectors and usage information.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
inputYesInput text to embed. Can be a single string, an array of strings, or token arrays. The text to embed into a numerical vector representation.
modelNoThe embedding model to use. Options: 'text-embedding-3-small' (default, cost-efficient), 'text-embedding-3-large' (higher quality), 'text-embedding-ada-002' (legacy).text-embedding-3-small
dimensionsNoOptional output embedding size. Supported by text-embedding-3 models. Reduces the embedding dimensions while maintaining quality.
encoding_formatNoThe format of the returned embeddings. 'float' returns floating-point numbers (default), 'base64' returns base64-encoded data.float

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Without annotations, the description carries the full burden. It mentions the return format (JSON with vectors and usage) but does not disclose potential behavioral traits like rate limits, maximum input length, or any side effects. For a nondestructive embedding tool, this is adequate but not exceptional.

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?

The description is well-structured with a clear opening, bulleted use cases, and a returns line. It is slightly redundant (first sentence and second sentence overlap), but overall concise and front-loaded.

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?

Given the tool's complexity (4 params, output schema present), the description covers purpose, use cases, and return type. It does not mention error handling or prerequisites, but the presence of an output schema and detailed schema descriptions compensates for these omissions.

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 baseline is 3. The description adds no additional parameter details beyond the schema; the intro and use cases are generic. The schema already adequately describes all four parameters.

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?

The description clearly states the tool creates text embeddings using OpenAI models, with specific verb 'Create' and resource 'embeddings'. It distinguishes from sibling tools like chat completion and image generation by focusing on vector representations for semantic search and clustering.

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?

The description provides explicit 'Use this when' bullet points covering key use cases (semantic similarity, search, ML tasks). However, it lacks exclusionary guidance or alternatives, such as noting that for text generation one should use openai_chat_completion.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AceDataCloud/OpenAIMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server