Skip to main content
Glama
Sign In
brewpage-mcp

brewpage-mcp

by kochetkov-ma
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search public gallery

search_gallery
Read-only

Search the BrewPage public gallery with text queries, pagination, date or view sorting, and optional owner-only filtering.

Instructions

Search the BrewPage public gallery. Optional filters: text query, pagination, sort, and 'mine' (owner-scoped, requires owner token).

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

Input Schema

NameRequiredDescriptionDefault
qNoFree-text search query
mineNoIf true, restricts results to entries owned by the supplied owner token
pageNoPage number (1-based; default 1)
sizeNoPage size (1-100; backend caps at 100)
sortNoSort order: 'date' or 'views'
ownerTokenNoOwner token; only sent as X-Owner-Token when 'mine' is true. Default: env BREWPAGE_OWNER_TOKEN (local server only).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.16.3
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Owner token; only sent as X-Owner-Token when 'mine' is true. Default: BREWPAGE_OWNER_TOKEN."New value: +"Owner token; only sent as X-Owner-Token when 'mine' is true. Default: env BREWPAGE_OWNER_TOKEN (local server only)."
  2. Changed3 schema fields 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"
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
  3. Changed1 schema field changedv1.13.0
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Owner token; only sent as X-Owner-Token when 'mine' is true"New value: +"Owner token; only sent as X-Owner-Token when 'mine' is true. Default: BREWPAGE_OWNER_TOKEN."
  4. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so the safety profile is covered. The description adds one genuine behavioral fact beyond the schema — the result set is the *public* gallery — plus the owner-token requirement for 'mine'. It says nothing about result shape, caps on returned fields, or rate limiting, so the addition is modest.

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?

Two short sentences with the purpose front-loaded and the filter summary second. It is tight overall, though the parameter enumeration in sentence two partly duplicates what the schema already shows.

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?

A zero-required-parameter read-only search with full schema coverage and an existing readOnlyHint does not need much prose, and this covers scope plus the owner-token dependency. Only minor gaps remain (default ordering, what a result entry contains), which the schema and annotations largely absorb.

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% and every parameter (q, mine, page, size, sort, ownerToken) is documented in-schema with constraints and enum values. The description only re-lists the same parameters by category, adding no syntax, format, or interaction detail beyond the schema; baseline 3 is correct.

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 and resource ('Search the BrewPage public gallery'), which is enough to distinguish it from the publish_/get_ siblings and from set_visibility. It stops short of explicitly naming a sibling to prefer for owner-scoped or paginated lookups, but the purpose itself is unambiguous.

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: the agent learns the tool accepts text query, sort, pagination, and an owner-scoped 'mine' mode, and that 'mine' requires an owner token. There is no explicit when-to-use/when-not or alternative ('use get_page for a known slug'), so the agent must infer the selection criteria.

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