Skip to main content
Glama
zwczwczwc

Chroma MCP Server

by zwczwczwc

chroma_update_documents

Update documents in a Chroma collection by specifying IDs and optionally modifying embeddings, metadata, or document content.

Instructions

Update documents in a Chroma collection.

Args:
    collection_name: Name of the collection to update documents in
    ids: List of document IDs to update (required)
    embeddings: Optional list of new embeddings for the documents.
                Must match length of ids if provided.
    metadatas: Optional list of new metadata dictionaries for the documents.
               Must match length of ids if provided.
    documents: Optional list of new text documents.
               Must match length of ids if provided.

Returns:
    A confirmation message indicating the number of documents updated.

Raises:
    ValueError: If 'ids' is empty or if none of 'embeddings', 'metadatas',
                or 'documents' are provided, or if the length of provided
                update lists does not match the length of 'ids'.
    Exception: If the collection does not exist or if the update operation fails.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idsYes
documentsNo
metadatasNo
embeddingsNo
collection_nameYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It states that the tool updates documents and raises ValueError if inputs are mismatched, but it doesn't disclose behavioral traits such as whether updates are full replacements or incremental, whether the operation is idempotent, or any permission requirements. It adequately describes error conditions but lacks broader behavioral context.

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 description is well-structured with bullet points for args, returns, and raises. It is front-loaded with the core purpose and is fairly concise, though the 'Args:' header and bullet format could be slightly tighter without losing clarity.

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?

Given the tool has 5 parameters, no output schema, and no annotations, the description covers the input semantics, return type, and error conditions reasonably well. However, it lacks details on overall behavior like incremental vs full updates, idempotency, or prerequisites such as collection existence (though implied by exception). It is mostly complete for an update tool.

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

Parameters5/5

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

Schema description coverage is 0%, yet the description provides detailed explanations for each parameter, including constraints like 'Must match length of ids if provided.' This adds significant meaning beyond the schema's property titles and types.

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 states 'Update documents in a Chroma collection' which is a specific verb+resource. It clearly distinguishes from sibling tools like add_documents (add new), delete_documents (delete), query_documents (query), etc.

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 description explains what can be updated (embeddings, metadatas, documents) but does not provide explicit guidance on when to use this tool vs alternatives like add_documents (for new documents) or modify_collection (for collection settings). Usage is implied but not clearly contrasted.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zwczwczwc/chroma-mcp-ollama'

If you have feedback or need assistance with the MCP directory API, please join our Discord server