Skip to main content
Glama

Embeddings, Rerank & Speech-to-Text (Tanod)

embed_texts

Read-onlyIdempotent

mlpeek: Create text embeddings. For images too use embed_multimodal; for pair scores use text_similarity. Returns 384-dimension embeddings of 1-64 texts with bge-small-en-v1.5 (English) or multilingual-e5-small (about 100 languages), normalised by default; input_type applies the model's query or passage prefix. Each text is cut at the model's 512-token window (truncated says so); over 16,384 tokens per request is a 422 too_many_tokens (not charged). Runs an open model pinned by hash on Tanod's own CPU (no LLM, no third-party API); an unavailable model is a 503 (not charged). Typically 20 ms for one short text, up to about 10 s at the token budget. Price: USD 0.0005 per text, at least USD 0.001 per call (1-64 texts per call: USD 0.001-0.032). Free: 5 mlpeek calls per IP per UTC day. The submitted text is never logged or stored. Docs: https://tanod.dev/learn/text-embeddings-api-no-account.html

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": {
      "texts": "<texts>"
    },
    "name": "embed_texts"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelNosmall-en = BAAI/bge-small-en-v1.5 (English); multilingual = intfloat/multilingual-e5-small (~100 languages). 384 dimensions both.small-en
textsYes1-64 texts, each at most 8,000 characters; each is truncated at 512 tokens (reported per text). Priced per text, minimum USD 0.001 per call.
encodingNobase64 = little-endian float32 bytes.float
normalizeNoL2-normalise (cosine similarity = dot product).
input_typeNoRetrieval prefix: query / passage (e5: 'query: ' / 'passage: '; bge: its query instruction / nothing). none = symmetric use.none

Output Schema

NameRequiredDescriptionDefault
dataNo
noteNo
errorNoOnly on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object.
modelNo
usageNo
encodingNo
dimensionsNo
input_typeNo
normalizedNo
prefix_appliedNo
max_tokens_per_textNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changed
    • removedInput schema / properties / encoding / title
      Removed value: -"Encoding"
    • removedInput schema / properties / input_type / title
      Removed value: -"Input Type"
    • removedInput schema / properties / model / title
      Removed value: -"Model"
    • removedInput schema / properties / normalize / title
      Removed value: -"Normalize"
    • removedInput schema / properties / texts / title
      Removed value: -"Texts"
    • removedInput schema / title
      Removed value: -"embed_textsArguments"
    • removedOutput schema / properties / data / items
      Removed value: -{
      -  "properties": {
      -    "embedding": {
      -      "type": [
      -        "array",
      -        "string",
      -        "null"
      -      ]
      -    },
      -    "index": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "tokens": {
      -      "type": [
      -        "integer",
      -        "null"
      -      ]
      -    },
      -    "truncated": {
      -      "type": [
      -        "boolean",
      -        "null"
      -      ]
      -    }
      -  },
      -  "type": [
      -    "object",
      -    "null"
      -  ]
      -}
    • removedOutput schema / properties / model / properties
      Removed value: -{
      -  "alias": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "id": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "license": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "revision": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  },
      -  "source": {
      -    "type": [
      -      "string",
      -      "null"
      -    ]
      -  }
      -}
  2. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "data": {
      +      "items": {
      +        "properties": {
      +          "embedding": {
      +            "type": [
      +              "array",
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "index": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "tokens": {
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "truncated": {
      +            "type": [
      +              "boolean",
      +              "null"
      +            ]
      +          }
      +        },
      +        "type": [
      +          "object",
      +          "null"
      +        ]
      +      },
      +      "type": [
      +        "array",
      +        "null"
      +      ]
      +    },
      +    "dimensions": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "encoding": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "error": {
      +      "description": "Only on an error result: an object {code, message}, or the reason string of an x402 PaymentRequired object."
      +    },
      +    "input_type": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "max_tokens_per_text": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "model": {
      +      "properties": {
      +        "alias": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "id": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "license": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "revision": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "source": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "normalized": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "note": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "prefix_applied": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "usage": {
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  3. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, yet the description still adds substantial operational context: 512-token truncation with a `truncated` flag, a 422 too_many_tokens ceiling above 16,384 tokens, 503 on unavailable model, both 'not charged', latency expectations, pricing tiers, a 5-calls-per-IP-per-day free quota, and a no-logging privacy guarantee. The only gap is that the free-quota and per-call minimum interplay could be spelled out more crisply, but this is well beyond the annotation bar.

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?

Front-loaded with purpose and sibling routing before the operational detail, and every sentence carries real information. It is a dense single paragraph with some repetition of pricing facts already encoded in the schema, which costs it the top mark.

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

Completeness5/5

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

For a stateless embedding endpoint with an output schema present, the description covers everything an agent needs to call it correctly: inputs, truncation, failure modes, cost, rate limits, and latency. Return values are appropriately left to the output schema.

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 coverage is 100%, so the baseline is 3, but the description earns more by explaining what `input_type` actually does ('applies the model's query or passage prefix') and by tying model choice to language coverage and 384 dimensions. It stops short of explaining `encoding`'s base64 layout, which is left entirely to the schema.

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?

Opens with a specific verb+resource ('Create text embeddings') and immediately distinguishes itself from two named siblings: embed_multimodal for images and text_similarity for pair scores. An agent knows exactly what this tool produces (384-dim vectors) 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 Guidelines5/5

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

Explicitly routes the agent to alternatives with the condition that selects them: 'For images too use embed_multimodal; for pair scores use text_similarity.' It also states the retrieval-prefix convention via input_type, which is the main usage decision inside the tool itself.

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.