brewpage-mcp

Read JSON document

get_json

Read-only

Retrieve a published BrewPage JSON document by namespace and ID, optionally supplying a password to access protected content.

Instructions

Fetch a published BrewPage JSON document by namespace and ID.

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": {
      "namespace": "<namespace>",
      "id": "<id>"
    },
    "name": "get_json"
  }
}

Input Schema

Name	Required	Description
`id`	Yes	Document ID
`password`	No	Password if the document is protected
`namespace`	Yes	Document namespace

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

B3.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered and the bar is lower. The description adds the meaningful constraint that only published documents are fetchable, but says nothing about the password-protected case (what happens on a missing/wrong password) or failure behavior for unknown IDs.

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?

A single front-loaded sentence with zero filler and no repetition of the title. It is efficient, though its terseness leaves behavioral gaps that could have been addressed in one more clause.

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

Completeness3/5

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

For a simple three-parameter read tool with annotations and full schema coverage, the essentials are present. The gaps (protected-document behavior, not-found handling, and the published-vs-draft boundary) are minor but real, keeping it at minimum-viable rather than complete.

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 all three parameters including the optional password are documented in the schema. The description merely restates 'by namespace and ID' and adds no format, casing, or lookup semantics beyond the schema, so baseline 3 applies.

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?

States a specific verb ('Fetch'), a specific resource ('published BrewPage JSON document'), and the scoping keys used to identify it. It reasonably separates itself from get_kv/get_page/get_stats by naming the 'JSON document' resource type, though it does not explicitly contrast with siblings.

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 versus get_page or get_kv, nor on prerequisites. The word 'published' hints that unpublished/draft documents are out of scope, but this is left implicit rather than stated as a usage rule.

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