brewpage-mcp

Get platform statistics

get_stats

Read-only

Retrieve BrewPage platform-wide usage statistics, including page count, file count, and storage usage, with an optional timezone to define the daily boundary.

Instructions

Get BrewPage platform-wide usage statistics including page count, file count, and storage usage. Counts use disjoint split: alive_public + alive_private + deleted == total. Optional tz shifts the 'today' boundary to the given IANA zone (default UTC).

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

Input Schema

Name	Required	Description	Default
`tz`	No	Optional IANA timezone id for the 'today' boundary, e.g. 'Europe/Lisbon'. Defaults to UTC. Invalid value falls back to UTC silently.

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.15.0Oct 27, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

First observedv0.1.0Oct 23, 2026

TDQS

A4/5.0

Behavior4/5

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

readOnlyHint already covers safety, but the description adds real behavioral context beyond annotations: the disjoint-split invariant (alive_public + alive_private + deleted == total) tells the agent how to interpret and reconcile the numbers. The tz default/fallback detail slightly duplicates the schema, keeping it from a 5.

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?

Three short sentences, front-loaded with what is returned, then the count invariant, then the tz caveat. No filler or repetition of the tool title.

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?

With no output schema, the description carries the burden of describing return content, and it does so by naming the metrics and the count invariant. It falls short only in not indicating whether the counts are scoped by the caller's token/account or truly global across the platform.

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 coverage is 100%, so the single tz parameter is fully documented in the schema, including the default and silent fallback. The description restates the same facts (default UTC, shifts 'today' boundary) rather than adding syntax or edge cases beyond it, so the 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?

States a specific verb (get) plus a precisely scoped resource (platform-wide usage statistics) and enumerates the metrics returned (page count, file count, storage usage). This separates it clearly from siblings like get_limits, which concerns quotas rather than aggregate usage.

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?

Usage is implied by 'platform-wide usage statistics' and the description implicitly tells the agent this is an aggregate read-only snapshot, but it never states when to call it versus get_limits or names any alternative/exclusion. The tz note explains how to adjust the tool, not when to choose it.

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