Skip to main content
Glama

list_my_white_label_galleries

List the authenticated user's white-label galleries. Requires auth.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden, and it does disclose the key non-obvious trait: authentication is required. It says nothing about ordering, pagination, whether empty galleries are included, or what the result set looks like, which an agent would want for a list operation.

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?

Two short sentences, the resource and scope front-loaded, and the auth requirement stated immediately after. There is no filler, redundancy, or tangential detail.

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 zero-parameter read tool with no annotations and no output schema, the definition covers the essentials: what it returns (galleries), whose (the caller's), and the auth requirement. The main residual gap is that, absent an output schema, it could say a bit about the shape or size of the returned list.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the schema-based baseline of 4 applies. Nothing in the description conflicts with or needs to compensate for the empty schema.

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?

The description gives a specific verb ("List") and a specific resource ("white-label galleries") and scopes it to the authenticated user's own galleries, which distinguishes it from the singular get_white_label_gallery sibling. It doesn't explicitly name that sibling, but the "my"/singular distinction is inferable from the text itself.

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 by the possessive "my": the agent can infer this is for enumerating the caller's own galleries rather than fetching one. There is no explicit "use this when..." framing, no mention of when to prefer get_white_label_gallery instead, and no prerequisites beyond auth.

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