azure-utils-mcp

cosmosdb_read_item

Retrieve a single item from Azure Cosmos DB by providing the item ID and partition key. Returns the item document as JSON for efficient point reads.

Instructions

Read a single item from a Cosmos DB container by ID and partition key.

Returns the full item document as JSON. Both item_id and partition_key are required — Cosmos DB requires the partition key for efficient point reads.

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>",
      "container": "<container>",
      "item_id": "<item_id>",
      "partition_key": "<partition_key>"
    },
    "name": "cosmosdb_read_item"
  }
}

Input Schema

Name	Required	Default
`account`	Yes
`database`	Yes
`container`	Yes
`item_id`	Yes
`partition_key`	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/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 full burden. It discloses that the tool returns the full item document as JSON and explains key-based vs. DefaultAzureCredential auth. This adds useful 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise (4 sentences) with no redundant information. Key points are front-loaded: purpose, requirements, and auth behavior.

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 presence of an output schema, the description adequately covers required parameters, auth, and return type. It lacks explicit error handling or 'not found' behavior, but remains sufficient for typical use.

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 0%. The description adds meaning for item_id, partition_key, and key_env_var, but does not describe account, database, or container, which are self-explanatory but still lacking explicit documentation.

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 explicitly states 'Read a single item from a Cosmos DB container by ID and partition key,' which is a specific verb and resource. It clearly distinguishes from sibling tools like cosmosdb_delete_item and cosmosdb_query_items.

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 that both item_id and partition_key are required and why, and discusses auth behavior via key_env_var. However, it does not explicitly state when to use this tool versus alternatives like cosmosdb_query_items for multiple items.

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

Deploy Server