Skip to main content
Glama

ninerouter_embed

Generate embeddings for text, text batches, or token inputs to support semantic search, clustering, and similarity analysis.

Instructions

Create embeddings for text, text batches, or supported token inputs.

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": {
      "model": "<model>",
      "input": "<input>"
    },
    "name": "ninerouter_embed"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYes
modelYes
optionsNoAdditional fields supported by the selected 9Router endpoint.
dimensionsNo
encoding_formatNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

Annotations already declare openWorldHint=true, idempotentHint=false and readOnlyHint=false, so the description needed to explain the surprising non-read-only framing of what is conceptually a lookup operation, plus cost, rate limits, or whether repeated calls with the same input are deduplicated. It does none of that. The only added semantic content is the mention of token inputs, which is a statement about accepted input formats rather than behavior.

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?

One short sentence, front-loaded with the verb and resource, with no filler or redundancy. It is efficient, though efficiency here partly reflects how little it commits to saying.

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?

For a five-parameter, nested-schema tool with no output schema, the definition is thin: it never explains that the result is a vector per input, how `dimensions` affects that, or how batches map to returned items. Given there is no output schema to fall back on, these are meaningful omissions, though the core call intent is at least unambiguous.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With five parameters and only 20% schema description coverage, the description carries most of the burden, yet it only gestures at the `input` union. It says nothing about `model` (required, max 512 chars), `dimensions` (which changes output vector length), or `encoding_format` (the one enum, float vs base64). An agent must reverse-engineer these from an undocumented schema.

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 gives a specific verb and resource ("Create embeddings") and enumerates the input shapes the tool accepts: text, text batches, and supported token inputs. This clearly separates it from siblings like ninerouter_chat or ninerouter_generate_image, though it never names an alternative explicitly.

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: nothing about when embeddings are preferable to ninerouter_chat, how to pick a model, or what 'supported' token inputs means in practice. The agent gets a purpose but no selection criteria.

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