Baasix MCP Server

baasix_collection_stats

Get collection statistics and analytics for specific Baasix collections over a chosen timeframe. Monitor usage trends and data growth to inform decisions.

Instructions

Get collection statistics and analytics

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": "baasix_collection_stats"
  }
}

Input Schema

Name	Required	Description	Default
`timeframe`	No	Timeframe for stats (e.g., "24h", "7d", "30d")
`collections`	No	Specific collections to get stats for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.7Aug 30, 2026

TDQS

C2.9/5.0

Behavior2/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 of behavioral disclosure. 'Get' implies a read-only operation, but the description does not state what metrics are returned, whether the operation is expensive or cached, what happens when optional parameters are omitted, or whether permissions are required.

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 one short, parseable sentence with no filler, and the key subject ('collection statistics') is front-loaded. Minor redundancy exists since 'analytics' largely overlaps with 'statistics', but overall it is appropriately concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and no annotations, the description omits the shape of the returned statistics, the default scope when collections is omitted, and how timeframe affects the results. This is enough to guess the tool's purpose but not enough for an agent to invoke it confidently.

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 100%, so the schema already documents both timeframe and collections parameters. The description adds no additional meaning about how these parameters affect the statistics returned.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear verb ('Get') and names a specific resource ('collection statistics and analytics'), making it identifiable as a read/analytics tool. However, 'analytics' is broad and it does not explicitly distinguish itself from sibling tools like baasix_generate_report or baasix_server_info.

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?

There is no guidance on when to use this tool versus alternatives. An agent must infer from the name that it is the appropriate choice for collection-level statistics, with no comparison to baasix_list_items, baasix_get_item, or baasix_generate_report.

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

Deploy Server