Skip to main content
Glama
Diogenes Gemini Suite & Autonomous Agents MCP

Diogenes Gemini Suite & Autonomous Agents MCP

gemini_vector_embeddings

Generate 3072-dimensional semantic vector embeddings from text to power RAG retrieval and agent memory. Use Gemini Embedding 2 for accurate similarity search.

Instructions

Generates 3072-dimensional semantic vector embeddings via Gemini Embedding 2 for RAG and agent memory.

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": {
      "text": "<text>"
    },
    "name": "gemini_vector_embeddings"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to embed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.4.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the output dimensionality (3072) and model lineage, which goes beyond the schema, but says nothing about return format (float array), input token limits, cost, or rate limits.

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?

A single front-loaded sentence with zero filler. The most decision-relevant facts (what it produces, dimension, model, purpose) all appear immediately.

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

Completeness4/5

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

For a one-parameter embedding tool with no output schema, the description covers the essentials and even hints at the output shape via the 3072 dimension. It stops short of input constraints or return-format specifics, but nothing critical is missing for correct invocation.

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% and the single 'text' parameter is documented in the schema as 'Text to embed'. The description adds no parameter-level detail (e.g., max length, encoding), so the baseline 3 for a fully-covered schema is correct.

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?

States a specific verb ('Generates') and resource ('3072-dimensional semantic vector embeddings'), plus the underlying model (Gemini Embedding 2). The embedding modality is unambiguous and clearly distinct from the search, generation, image, and media siblings.

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?

The trailing phrase 'for RAG and agent memory' implies the intended use context, which is better than nothing. However, it names no alternatives and gives no when-not guidance (e.g., no batch vs single-text routing, no fallback model), so usage is only implied.

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