Skip to main content
Glama

list_public_artworks

Browse the public AirGallery discover feed. Returns artworks with image URLs, prompts, tags, and creator info. Supports pagination.

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_public_artworks"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNoFilter by tag
limitNoMax results (default 20, max 100)
offsetNoPagination offset (default 0)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It usefully discloses the payload contents (image URLs, prompts, tags, creator info) and that pagination exists, which tells the agent this is a read-only browse. It does not state whether authentication is required, whether results are ordered, or how the feed is ranked.

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?

Three short sentences with the resource scope front-loaded, then the return shape, then a capability note. No filler, no repetition of the tool name.

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 simple three-parameter read-only list tool: purpose, return contents, and pagination are all covered, and the schema handles parameter detail. The only gap is behavioral context such as auth requirements or result ordering, which is minor for a discover-feed browse.

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 are already documented including the default 20 / max 100 limit and offset semantics. The description adds only "supports pagination," restating what the schema covers, 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 and resource ("Browse the public AirGallery discover feed") and even enumerates the returned fields. The word "public" implicitly separates it from list_my_artworks, though it never names that sibling explicitly.

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 by "public discover feed" — an agent can infer this is for browsing other people's artworks rather than its own. There is no explicit statement of when to prefer it over list_my_artworks or get_artwork, and no preconditions or exclusions.

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