azure-utils-mcp

cosmosdb_list_containers

List all containers in a Cosmos DB database by providing the account and database name. Returns a sorted JSON array of container names, supporting key-based or Azure credential authentication.

Instructions

List all containers in a Cosmos DB database.

Returns a sorted JSON array of container names. The account can be given as a short name or full endpoint URL.

key_env_var: name of the environment variable holding the Cosmos DB account key. If the variable is set, key-based auth is used; otherwise DefaultAzureCredential is used.

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": {
      "account": "<account>",
      "database": "<database>"
    },
    "name": "cosmosdb_list_containers"
  }
}

Input Schema

Name	Required	Default
`account`	Yes
`database`	Yes
`key_env_var`	No	AZURE_COSMOS_KEY

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0May 28, 2026

TDQS

A4.1/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the result is a sorted JSON array, and describes authentication behavior based on environment variable presence. This is useful beyond the schema, though it doesn't explicitly state that the operation is read-only.

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 concise with three short paragraphs. The first sentence clearly states the purpose, followed by the return format and authentication details. Every sentence adds value, though it could be slightly more compact.

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's simplicity and the presence of an output schema, the description adequately covers parameter semantics, authentication, and return type. It doesn't need to explain return values further. The description is complete for a list operation.

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

Parameters4/5

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

With 0% schema description coverage, the description adds critical meaning: account can be a short name or full endpoint, database is the database name, and key_env_var has a default and explains the authentication logic. This compensates well for the lack of schema descriptions.

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 tool lists all containers in a Cosmos DB database, using a specific verb and resource. It also notes the sorted JSON array return, differentiating it from sibling tools like cosmosdb_get_container_info.

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 authentication methods (key vs DefaultAzureCredential) but does not explicitly state when to use this tool versus other Cosmos DB tools like cosmosdb_list_accounts or cosmosdb_query_items. Usage context is implied but no exclusions or alternatives are given.

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

Deploy Server