Skip to main content
Glama

get_white_label_gallery

Get a public white-label gallery by slug.

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": {
      "slug": "<slug>"
    },
    "name": "get_white_label_gallery"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesGallery slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add one genuinely useful behavioral fact beyond the name/schema: only public galleries are reachable by slug, so private or unlisted ones are out of scope. It says nothing about failure behavior for a missing slug, access requirements, or what the response contains.

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?

A single ten-word sentence with the resource and the lookup key front-loaded and zero filler. Nothing is wasted and nothing needs restructuring.

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 one-parameter read tool with 100% schema coverage and no output schema, the essentials for invoking it correctly are present. It is however bare: an agent gets no sense of what a gallery object contains or how a not-found slug surfaces, which matters more here because no annotations supply that context.

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 the single parameter 'slug' is already documented as 'Gallery slug'. The description reinforces that the slug is the lookup key but adds no format, casing, or derivation guidance beyond what the schema provides, so the 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 ('Get'), a specific resource ('public white-label gallery'), and the lookup key ('by slug'). The qualifier 'public' implicitly distinguishes it from list_my_white_label_galleries, but the distinction is only implied rather than asserted, so it falls short of a 5.

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 only implied: 'public' signals that this retrieves publicly visible galleries, contrasting with the ownership-scoped sibling list_my_white_label_galleries. There is no explicit when-to-use, when-not-to-use, or named alternative, and no mention of what to do when a slug is unknown.

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.

Resources