Skip to main content
Glama

x402 Data API (Crypto, DeFi, SEC EDGAR, Search, Embeddings, Whisper, OCR)

ai_embed

[$0.001] Compute dense 768-dimensional semantic embedding vectors and L2 norms using local Ollama nomic-embed-text (~300 MB VRAM) for clustering, similarity, and RAG.

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

Input Schema

NameRequiredDescriptionDefault
textYesText to embed into a 768-dim vector

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose meaningful traits: a cost of $0.001, execution via local Ollama, ~300 MB VRAM footprint, and that L2 norms are returned alongside vectors. It omits error behavior, batching, and whether text exceeding the 12,000-char limit is truncated or rejected.

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?

One sentence, front-loaded with the cost marker and the core action, followed by model details and use cases. Nothing is redundant or padded.

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?

For a single-parameter tool with no output schema, the description supplies cost, execution environment, dimensionality, and expected outputs. Only minor gaps remain around failure modes and handling of oversized input.

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% and the single 'text' parameter is fully documented in the schema, including the 12,000-character maxLength. The description adds no format or preprocessing hints beyond what the schema already states, 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 and resource ('compute dense 768-dimensional semantic embedding vectors and L2 norms') with the backing model named. It clearly separates this from non-embedding siblings like ai_summarize or ai_ocr, though it never names an alternative tool for overlapping needs such as search_semantic.

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?

The phrase 'for clustering, similarity, and RAG' implies intended downstream uses, which is reasonable context. However, there is no explicit when-to-use vs. when-not guidance and no pointer to siblings like search_semantic that also deal with semantic similarity.

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