Skip to main content
Glama

Text To Embedding Price

text_to_embedding_price

Calculate price for text embedding generation.


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

Input Schema

NameRequiredDescriptionDefault
inputYesText string or list of text strings for price calculation
modelNoEmbedding model nameBge_M3_FP16

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden; it discloses a useful behavioral constraint (Bge_M3_FP16 accepts ≤8192 tokens per input) but says nothing about whether the call is free, whether it consumes credits, what happens with oversized input, or how pricing is derived. For a pricing tool the cost side-effect question is exactly what an agent needs and it is left unanswered.

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 purpose sentence is front-loaded and the model constraint is presented as a compact list with no filler. The '---' separator is slightly noisy but costs nothing in comprehension.

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

Completeness3/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 input shape is fully described by the schema. However, for a no-annotation tool that touches billing logic, the description omits the one thing an agent would need to act safely: whether this call itself incurs cost and how the estimate relates to actually invoking text_to_embedding.

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 description coverage is 100%, so the schema already documents both `input` and `model`, establishing a baseline of 3. The model list with the ≤8192-token limit adds a small amount of meaning beyond the schema, but it duplicates the default value and covers only one of the models the `model` string parameter presumably accepts.

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 and resource ("Calculate price for text embedding generation"), which cleanly separates it from the sibling generation tool text_to_embedding by signaling this is a cost quotation rather than execution. It is clear without needing to name the sibling explicitly, though an explicit contrast would push it higher.

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 only implied: the word "price" suggests calling this before generating embeddings to estimate cost, but the description never says when to call it versus text_to_embedding, nor whether it is a prerequisite to a paid call. No exclusions or preconditions are given.

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.