Skip to main content
Glama

list_my_artworks

List the authenticated user's saved artworks (private gallery). 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_artworks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax results (default 20)
offsetNoPagination offset

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?

With no annotations, the description carries the full load: it discloses that authentication is mandatory and that results are drawn from a private gallery, which is useful behavioral context. It omits other relevant traits such as result ordering, default page size behavior beyond the schema's 'default 20', and what happens when the collection is empty.

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, front-loaded with the scope and followed by the auth precondition, with no filler. It is appropriately terse for a simple listing tool.

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 two-parameter read-only listing tool with complete schema coverage and no output schema, the description supplies the scope and auth requirement an agent needs. Only minor gaps remain around ordering and exhaustive alternatives.

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?

Both parameters (limit, offset) are fully documented in the schema at 100% coverage, so the baseline of 3 applies. The description adds no extra meaning about pagination semantics or any cap on limit.

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 ('List') and resource ('saved artworks') scoped to the authenticated user, with the parenthetical '(private gallery)' clarifying it is the user's own collection rather than public content. This is enough to separate it from list_public_artworks by scope, though it does not name 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?

The 'Requires auth' clause establishes the prerequisite for calling the tool, which is genuine usage guidance. However, it never states when to choose this over list_public_artworks or how it relates to gallery-specific tools, leaving the selection decision to inference from the word 'private'.

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