Skip to main content
Glama
Sign In
brewpage-mcp

brewpage-mcp

by kochetkov-ma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get upload limits

get_limits
Read-only

Retrieve BrewPage API limits for request size, per-type sizes/counts/TTLs, site ZIP/file constraints, and profile or token TTL caps before publishing content.

Instructions

Get the current BrewPage limits (GET /api/limits): request size; per type (html, json, kv, files, sites) max size, counts and TTL default/maximum; profileMaxTtlDays (TTL cap for a token in a profile); site ZIP expansion, path and name lengths, allowed file extensions and skipped system files. Sizes are bytes, TTLs days. The answer always has reach: profile only when the owner token is active in a profile, else token (also with no token). With a usable owner token also ownerMaxTtlDays.

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_limits"
  }
}

Input Schema

NameRequiredDescriptionDefault
ownerTokenNoOwner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.3
    • addedInput schema / properties / ownerToken
      Added value: +{
+  "description": "Owner token from create. Default: env BREWPAGE_OWNER_TOKEN (local server only).",
+  "type": "string"
+}
  2. Changed1 schema field changedv1.15.0
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv1.12.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description adds real behavioral context beyond that: the required HTTP route, units (bytes/days), and the fact that the returned scope block varies with whether an owner token is active in a profile or absent entirely. That conditional-shape disclosure is exactly the kind of context annotations cannot carry.

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?

Front-loaded with the verb, resource, and route, followed by a dense but well-ordered enumeration of returned fields using semicolons. It is packed into long clauses and the phrase 'The answer always has reach' is slightly opaque, but nearly every clause carries information.

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 full burden of describing return values and does so thoroughly: per-type limits, counts, TTL defaults/maxima, profileMaxTtlDays, site ZIP rules, and the conditional scope fields. Only the exact JSON shape remains unspecified, which is a minor gap for a read-only lookup.

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?

Schema coverage is 100% and the single parameter's default (env BREWPAGE_OWNER_TOKEN) is already documented there. The description still adds meaning by explaining what the token changes in the result: `profile` scope only when the owner token is active in a profile, and `ownerMaxTtlDays` only with a usable owner token.

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 and resource ('Get the current BrewPage limits') plus the underlying endpoint, then enumerates the returned fields (sizes, counts, TTLs, ZIP rules, extensions). No sibling returns limits, so the purpose is unmistakable without opening the schema.

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 rather than stated: an agent infers it should call this to learn constraints before publishing, but the description never says when to use it or why (e.g., 'call before publish_file to pick a valid size'). The conditional notes about `profile` vs `token` describe response shape, not invocation guidance.

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

Deploy Server

Other Tools