Skip to main content
Glama

Text To Embedding Price

text_to_embedding_price

Calculates the cost of generating text embeddings from one or more input strings before you run the request.

Instructions

Calculate price for text embedding generation.

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 observedv0.6.3

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden and does not meet it. It does not say whether the call itself is free, whether pricing is per character/token or per request, whether batching multiple strings changes the total, or what model families are accepted. The only mitigation is that an output schema exists, which covers the return shape.

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?

A single front-loaded sentence with zero filler and no redundancy. It is appropriately sized as a sentence, though the brevity is achieved by omission rather than by tight editing of richer content.

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?

The tool is structurally simple (2 params, one required, output schema present), so the description does not need to explain return values. However, for a pricing tool the essential context — cost unit, whether calls are billable, and the array-versus-string pricing model — is absent, leaving an agent able to invoke it but not to interpret or plan around it.

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 both parameters (input as string or array, model with default 'Bge_M3_FP16') are already documented in the schema. The description adds no meaning beyond that — notably it does not explain the pricing consequence of passing an array versus a single string, which is the one non-obvious semantic here. 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?

The description pairs a specific verb with a specific resource: 'Calculate price for text embedding generation.' That makes it distinguishable from the sibling text_to_embedding (which generates embeddings) and from the other modality-specific *_price tools. It falls short of a 5 only because it never names the sibling it complements or states that it quotes cost rather than performing the operation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

There is no when-to-use guidance at all: no statement that this should be called before text_to_embedding to estimate cost, no prerequisite checks (e.g. fetch_balance, get_available_models), and no exclusions. The agent must infer usage entirely from the tool name and the word 'price'.

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