nvidia-nim-mcp

create_embeddings

Turn text into vector embeddings using NVIDIA NIM models, enabling semantic search, retrieval-augmented generation, clustering, and similarity comparisons.

Instructions

Convert text(s) into vector embeddings using NVIDIA NIM embedding models. Useful for semantic search, RAG, clustering, and similarity comparisons.

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": "create_embeddings"
  }
}

Input Schema

Name	Required	Description
`input`	Yes	Text or list of texts to embed
`model`	No	Embedding model ID (e.g. nvidia/nv-embed-v1)
`truncate`	No
`encoding_format`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv2.1.1Aug 14, 2026

TDQS

A3.5/5.0

Behavior2/5

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It only restates the conversion action and lists use cases; it does not mention default model behavior, truncation handling, output format specifics, rate limits, or other operational traits. This is a limited disclosure beyond the name.

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?

The description is a single, well-structured sentence that front-loads the core action and resource before adding valuable use-case context. Every word earns its place; there is no redundancy or filler.

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

Completeness2/5

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

With no output schema and no annotations, the description does not explain return value shape, default model/truncation settings, or how the optional parameters affect behavior. It is adequate for a high-level understanding but insufficient for reliable invocation in complex scenarios.

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?

The schema describes 'input' and 'model', but 'truncate' and 'encoding_format' are only enums without detailed descriptions. The tool description adds no parameter-level meaning and does not compensate for the 50% schema coverage gap. It merely restates that text is converted, which is already implied by the 'input' parameter.

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?

The description uses a specific verb ('Convert') and identifies the exact resource ('text(s) into vector embeddings using NVIDIA NIM embedding models'). It clearly distinguishes from sibling tools like chat_completion and rerank_passages by stating the core function.

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

Usage Guidelines4/5

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

The description provides concrete use cases ('semantic search, RAG, clustering, and similarity comparisons') that signal when to use this tool. It lacks explicit exclusionary guidance or comparison to alternatives, but the context is clear enough for the agent to select it appropriately.

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

Deploy Server