Skip to main content
Glama
BrianDeacon

cosmosdb-mcp

by BrianDeacon

cosmosdb_count_items

Count items in a Cosmos DB container. Optionally filter with a SQL WHERE clause to count specific items.

Instructions

Count items in a Cosmos DB container, with an optional filter.

where accepts a SQL WHERE clause body (without the WHERE keyword), e.g.: c.status = 'active' c.createdAt > '2025-01-01'

If where is omitted, counts all items in the container. Returns a JSON object with a 'count' field.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
accountYes
databaseYes
containerYes
whereNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations were provided, but the description does not disclose any behavioral traits such as permissions needed, performance implications, or side effects. It only describes input/output without addressing costs or limitations.

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, front-loaded with the main purpose, and includes inline examples. Every sentence adds value without redundancy.

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?

The description explains the return format and optional filtering, and an output schema exists. It covers the core functionality but omits error scenarios or rate limits, which are minor given the tool's simplicity.

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 description adds significant meaning to the 'where' parameter with examples and default behavior, but the required parameters (account, database, container) lack additional context beyond their names. With 0% schema description coverage, the description partially compensates but not fully.

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 'Count items in a Cosmos DB container' using a specific verb and resource. It explicitly contrasts with siblings like cosmosdb_query_items (which returns items) and provides distinct functionality.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explains when to use the tool (counting with optional filter) and provides examples for the where clause. It implies alternative tools but does not explicitly state when not to use this tool.

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/BrianDeacon/cosmosdb-mcp'

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