Galatic.ai

List library

list_gallery

Read-onlyIdempotent

List the signed-in user's library, newest first: { items, nextKey, count } with signed media URLs; pass nextKey back as lastKey for the next page, keeping the same filters (cursors do not carry across filter changes). type filters by item type (image, video, audio, music, music-video, analysis), source by origin (e.g. "concierge"), since takes epoch milliseconds (not an ISO date). stats true ignores the rest and returns totals by type and the last 24 hours' count. Use fetch for one item, search to find by text. Read-only.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "context": "<context>",
      "llm_model": "<llm_model>"
    },
    "name": "list_gallery"
  }
}

Input Schema

Name	Required	Description
`type`	No	image, video, audio, music, music-video or analysis.
`limit`	No	Items per page (default 100).
`since`	No	Epoch milliseconds, e.g. "1767225600000". Not an ISO date.
`stats`	No	true: totals only.
`source`	No	Origin filter, e.g. "concierge".
`context`	Yes	Explain in 15-25 words, in third person, why this tool is called and how it supports the user's goal. For analytics only. You MUST describe only the abstract purpose of the tool call. NEVER include, repeat, paraphrase, or infer personal, sensitive, or identifying information from the user request or tool results, including names, emails, phone numbers, IPs, IDs, or credentials. You MUST generalize specific entities into roles such as "a user", "the customer", or "an account". Example: "Retrieving a customer's recent orders to investigate a billing issue and help support determine the appropriate resolution."
`lastKey`	No	nextKey from the previous page, same filters.
`llm_model`	Yes	The exact model identifier you (the assistant) are running as, taken from your system prompt or environment (e.g. "claude-opus-4-8", "gpt-5.2"). Used for analytics only. If you do not know your model identifier with certainty, pass "unknown" — never guess.
`conversation_id`	No	Pass the exact conversation_id from the server's previous response, unchanged. The server provides it on the first call — never invent one, and do not issue parallel tool calls until you have it. Keep passing the same conversation_id for the rest of the conversation, including after later user messages or on a different task; do not reset it when the user starts a new request.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedOct 27, 2026
- addedInput schema / properties / lastKey / description
```
Added value: +"nextKey from the previous page, same filters."
```
- addedInput schema / properties / limit / description
```
Added value: +"Items per page (default 100)."
```
- addedInput schema / properties / since / description
```
Added value: +"Epoch milliseconds, e.g. \"1767225600000\". Not an ISO date."
```
- addedInput schema / properties / source / description
```
Added value: +"Origin filter, e.g. \"concierge\"."
```
- addedInput schema / properties / stats / description
```
Added value: +"true: totals only."
```
- addedInput schema / properties / type / description
```
Added value: +"image, video, audio, music, music-video or analysis."
```
First observedOct 24, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description reinforces this with 'Read-only.' Beyond that it discloses non-obvious behavior: signed media URLs in the payload, cursors invalidated by filter changes, and stats=true ignoring the remaining parameters. It doesn't cover rate limits or how large a library page can grow, but the behavioral burden is largely met.

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?

Front-loaded with the resource and return shape, then pagination, then filters, then alternatives — a sensible funnel. A few clauses restate schema content (the type enumeration, the epoch-millisecond note appears twice), which is mild redundancy but not padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 9-parameter paginated list tool with no output schema, the description supplies the return contract, pagination protocol, filter semantics, and sibling routing. An agent has everything needed to call it correctly and to interpret the response.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: 'since' takes epoch milliseconds rather than an ISO date, 'stats true ignores the rest', and the lastKey/filter coupling that the schema only hints at ('same filters'). The type and source explanations largely duplicate the schema, keeping it from a 5.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb and resource plus ordering ('newest first') and an explicit return shape '{ items, nextKey, count }'. It also names what the tool is not ('Use fetch for one item, search to find by text'), so an agent can place it among siblings without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly routes to alternatives: fetch for a single item, search for text lookup. It also states the conditions that change behavior — pass nextKey back as lastKey with the same filters, and stats=true overrides all other filters — which is the kind of when-to-use guidance that prevents misuse.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Galatic.ai tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.