Skip to main content
Glama

Artworks by Ryan Seslow for image and 3D license

list_artworks
Read-only

Works by Ryan Seslow on aremes-enterprises.com/work/, each with its own page and image. Every work can be licensed as an image (one month, one year, or own it forever); some also as a 3D model. Returns slug, title, series, page, image, how it was made, and the license prices.

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

Input Schema

NameRequiredDescriptionDefault
queryNoOptional words to match in the title or series.

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that by naming the fields returned (slug, title, series, page, image, method, license prices) and the license durations, but says nothing about ordering, pagination, or result limits for an unfiltered list.

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, front-loaded with what the tool returns and its domain. The parenthetical of license terms is slightly incidental but still informative; no filler.

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?

With one optional parameter, no output schema, and read-only annotations, the description carries the return-shape burden itself and does so by listing the fields. Only the lack of guidance on how results are ordered or bounded keeps it from being fully 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 coverage is 100% for the single optional query parameter, so the schema already defines it as words matched against title or series. The description adds no further matching semantics or examples, so the baseline of 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 resource (works by Ryan Seslow at a named URL) and enumerates what each item carries: its own page, an image, and optionally a 3D model. The license framing distinguishes it from mutation siblings like start_image_license, though it does not explicitly name any sibling as an alternative.

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 explaining that every work can be licensed as an image or 3D model, it hints this is the discovery step before the start_* tools. There is no explicit when-to-use, when-not-to-use, or statement that the optional query filters results.

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