Skip to main content
Glama

List or search artworks

list_art
Read-only

List Veritas Silicea artworks (72 executable HTML+SVG pieces, newest first), optionally filtered by a search phrase over titles and descriptions. Free. Returns id, entry, title, date, description, good-for line, free preview URL and buy URL.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoOptional words to search for in titles and descriptions, e.g. "memory", "clock", "charge".
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, closed-world listing. The description adds useful behavior beyond that: the collection size, newest-first ordering, free access, search scope, and returned fields including preview and buy URLs. It does not contradict the annotations.

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?

The description is compact and front-loaded, stating the resource, ordering, optional search, cost, and return shape in a small number of dense sentences. Every clause contributes useful information, especially since there is no output schema.

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?

Because there is no output schema, the description usefully lists the returned fields, and it covers core search behavior. However, for a paginated listing tool with limit and offset parameters, it omits pagination semantics and does not provide guidance on choosing this tool over its siblings.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 33%, with meaningful descriptions present for query but not for limit or offset. The description restates the query behavior already covered by the schema and does not explain pagination, limits, defaults, or how offset interacts with newest-first ordering, so it does not compensate for the low schema coverage.

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 states a specific verb and resource: listing Veritas Silicea artworks, with an optional search filter over titles and descriptions. It is clear enough to distinguish this from a single-item retrieval like get_art, but it does not explicitly differentiate itself from the other sibling tools.

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 description implies usage for listing and searching artworks and notes that search is optional, but it gives no explicit when-to-use or when-not-to-use guidance relative to get_art, suggest_art, or the how-to tools. The context is adequate but leaves alternatives to inference.

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