Skip to main content
Glama

Search public gallery

search_gallery
Read-only

Search the public gallery by title. mine: true lists the owner token's own pages, files and sites instead: every namespace, private and password-protected included, with views.

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
qNoTitle substring
mineNo
pageNo
sizeNo
sortNo
ownerTokenNoNeeded with `mine`

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • removedInput schema / properties / mine / description
      Removed value: -"If true, restricts results to entries owned by the supplied owner token"
    • changedInput schema / properties / ownerToken / description
      Previous value: -"Owner token; only sent as X-Owner-Token when 'mine' is true. Default: env BREWPAGE_OWNER_TOKEN (local server only)."New value: +"Needed with `mine`"
    • removedInput schema / properties / page / default
      Removed value: -1
    • removedInput schema / properties / page / description
      Removed value: -"Page number (1-based; default 1)"
    • removedInput schema / properties / page / maximum
      Removed value: -9007199254740991
    • changedInput schema / properties / q / description
      Previous value: -"Free-text search query"New value: +"Title substring"
    • removedInput schema / properties / size / description
      Removed value: -"Page size (1-100; backend caps at 100)"
    • removedInput schema / properties / sort / description
      Removed value: -"Sort order: 'date' or 'views'"
  2. Changed1 schema field changed
    • 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)."
  3. Changed3 schema fields changed
    • 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
  4. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations only declare readOnlyHint=true, so the description must carry scope. It does: it discloses that `mine` spans every namespace including private and password-protected items, and returns views — non-obvious access semantics an agent could not infer. It does not mention authentication requirements beyond the implicit ownerToken or any result limits.

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 tight sentences, with the primary behavior front-loaded and the alternate mode immediately following. The trailing phrase "with views" is slightly ambiguous but the rest carries no waste.

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?

For a read-only, six-parameter search tool with no output schema, this covers the two semantically tricky parameters well and relies on the schema for pagination and sorting. A short note on combining `q` with `mine` or on result ordering would make it 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 only 33%, so the description has to compensate. It clarifies `q` (title substring) and the complex `mine` flag including its privacy/namespace implications, but says nothing about `page`, `size`, or `sort`, leaving three parameters to the schema alone.

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 public gallery by title." It then defines the alternate mode (`mine: true`) which effectively distinguishes this tool's two behaviors. No sibling tool is named, but none of the listed siblings is a search tool, so differentiation matters less here.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear mode-selection guidance: use `q` to search the public gallery by title, or set `mine: true` to enumerate the owner token's own pages, files and sites. It does not state exclusions (e.g., what happens if both q and mine are supplied), so it stops short of fully explicit when/when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.