Skip to main content
Glama
Sign In
infocepo-infra-mcp

infocepo-infra-mcp

by ynotopec
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

chromadb_collections

List all ChromaDB collections in the vector database for a specified environment (prod or lab). View available collections to manage your vector data.

Instructions

List all ChromaDB collections in the vector database.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "chromadb_collections"
  }
}

Input Schema

NameRequiredDescriptionDefault
envNoEnvironment: prod (default), lab

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description accurately implies a read-only operation. However, it does not mention potential performance impact or what exactly is returned (e.g., an array of names). Adequate but not comprehensive.

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 a single sentence with no wasted words. It is appropriately concise for a simple list operation, though could benefit from a brief structure with return value hint.

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?

Given the tool's simplicity (1 optional param, no output schema), the description mostly suffices. However, it omits the return format (e.g., list of collection objects), which is a gap for an agent without output schema.

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?

The only parameter 'env' is fully described in the input schema with enum values and default. The description adds no additional meaning beyond the schema, so baseline 3 applies.

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 clearly states the action ('list all collections') and the resource ('ChromaDB collections in the vector database'). It distinguishes from siblings like chromadb_search and chromadb_upsert, which target within collections or modify data.

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?

No guidance on when to use this tool versus alternatives. It does not mention that this is the initial step before search/upsert, or any prerequisites.

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

Deploy Server

Other Tools